-
Notifications
You must be signed in to change notification settings - Fork 711
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
Consider having kubeadm version annotations for Pod objects #1231
Comments
/assign @timothysc @luxas @fabriziopandini |
+1 |
At first I was concerned this would imply the pods to be restarted because the manifest would always change. However, that's fine because when upgrading kubeadm-based deployments you'll always have at least some updates to field in the pod, like image version (maybe except for So, big 👍 (modulo |
seems a bit too late to change in this cycle, but IMHO a nice to have. |
I debate if this has benefit in the future. |
/remove-help because it sounds as if there's some disagreement on whether this should be implemented. |
/close |
@fabriziopandini: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
SGTM. its a "nice-to-have safeguard" - viable if we reach another case where we have to mutate the manifests by knowning which version they were created with. hopefully not. |
as per the discussion here:
kubernetes/kubernetes#70893 (review)
the alternative to Pod metadata is to have comments in manifest files, but these have to be parsed.
cc @fabriziopandini @luxas @rosti
/kind design
/priority important-longterm
The text was updated successfully, but these errors were encountered: