-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Allow xcom sidecar container image to be configurable #26766
Conversation
This should be valid until the code is actually removed from the codebase.
This should be valid until the code is actually removed from the codebase.
a82cb8d
to
cf0c9a6
Compare
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. But we need to wait for @dstandish's re-review.
@dstandish @XD-DENG Any we can get this merged? Thanks in advance. |
ok lemme look |
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.
mainly one docs reqeust
Co-authored-by: Daniel Standish <[email protected]>
Co-authored-by: Daniel Standish <[email protected]>
We probably should not be configuring xcom settings from the hook in this way but for better or worse we've done it, first in apache#26766 and again in apache#28125. The problem is that other operators derived from KPO, e.g. GKEStartPodOperator, may use a different hook that doesn't have this xcom-specific methods. So KPO needs to tolerate that.
Hello, is this PR in any version released? I can't find the changes in the current version 2.6.3 or in the main-branch. |
Closes #10605.
Adding a configurable image value to the
KubernetesHook
which is used byPodDefaults.SIDECAR_CONTAINER.image
will allow both:alpine:latest
image with a specific tag.