-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add featuregate for k8s 1.28 native sidecar container #2801
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this makes sense... is there a way to write an e2e for this?
Sure, you'd need to add a new test suite and run it with the gate enabled. Then checking if the sidecar is an initContainer should be straightforward. |
@swiatekm whats the best way to configure a k8s featuregate for a specific e2e test suite? Do we need to create a new e.g. opentelemetry-operator/.github/workflows/e2e.yaml Lines 22 to 24 in a515234
Do we need then to create a new step like
|
You should do the same thing we do for enabling other options in e2e tests. See here. You do need to add a new entry to the e2e test matrix, because you need a separate operator deployment with the flag enabled. Then you add a make target that adds the command-line option to the operator Deployment (same as we do for other operator flags), and use that make target for setup in the e2e tests. |
// It needs to be enabled with +featureGate=SidecarContainers. | ||
// See: | ||
// https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features | ||
EnableNativeSidecarContainers = featuregate.GlobalRegistry().MustRegister( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could on k8s 1.28+ always use the native sidecar pattern and keep using the existing approach on older k8s versions.
This way no feature flag is needed and we would always use a recommended approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do that, but we would expect different results in our e2e tests. Which makes it hart to execute the same tests on both platform versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'm ok with that as well. I can't think of any issues it might cause.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, then I will enable it for the 1.28+ e2e tests. Would be nice it it makes it into v0.111.0.
5261059
to
f141dcb
Compare
f141dcb
to
c910e80
Compare
Seems we dont need to enable it in Kind.
|
c910e80
to
aebc2cb
Compare
aebc2cb
to
60e8a8e
Compare
30ba9b7
to
54bd8d4
Compare
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
54bd8d4
to
5773a44
Compare
containers: | ||
- name: myapp | ||
initContainers: | ||
- name: otc-container |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we verify that this has the correct restart policy?
.chloggen/native_sidecar.yaml
Outdated
change_type: enhancement | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. collector, target allocator, auto-instrumentation, opamp, github action) | ||
component: pkg/sidecar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
collector
.chloggen/native_sidecar.yaml
Outdated
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please document here the feature gate as a flag e.g. --
. Could you please document which k8s version support by default native sidecar?
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
f9df64a
to
9471885
Compare
Updated the changelog @pavolloffay |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
just some docs nits
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
Changed it to k8s 1.29 and we now mention in the fg desc that it should only be enabled on k8s v1.29+. |
Description:
Link to tracking Issue(s):
Testing:
Documentation: