Skip to content
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

Closed
neolit123 opened this issue Nov 12, 2018 · 9 comments
Closed

Consider having kubeadm version annotations for Pod objects #1231

neolit123 opened this issue Nov 12, 2018 · 9 comments
Labels
kind/design Categorizes issue or PR as related to design. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented Nov 12, 2018

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

@neolit123 neolit123 added this to the v1.14 milestone Nov 12, 2018
@k8s-ci-robot k8s-ci-robot added kind/design Categorizes issue or PR as related to design. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 12, 2018
@neolit123
Copy link
Member Author

/assign @timothysc @luxas @fabriziopandini
WDYT
(proposed by @fabriziopandini here)

@fabriziopandini
Copy link
Member

fabriziopandini commented Nov 30, 2018

+1
I think that making explicit that an object was created by kubeadm, tracking the last kubeadm version touched the object and when is a good practice.
It add transparency to what kubeadm does and open ups to add more robust version specific logic

@NicolasT
Copy link

NicolasT commented Feb 6, 2019

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 etcd if the preferred version and configuration doesn't change across kubeadm/K8s versions, which you may not want to restart without good cause?).

So, big 👍 (modulo etcd)

@timothysc timothysc added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Feb 7, 2019
@neolit123
Copy link
Member Author

seems a bit too late to change in this cycle, but IMHO a nice to have.
possibly early 1.15 we can get back to this.

@neolit123 neolit123 modified the milestones: v1.14, v1.15 Mar 2, 2019
@timothysc timothysc modified the milestones: v1.15, Next May 10, 2019
@timothysc timothysc added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels May 10, 2019
@timothysc timothysc added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 10, 2019
@timothysc
Copy link
Member

I debate if this has benefit in the future.

@astrieanna
Copy link

/remove-help

because it sounds as if there's some disagreement on whether this should be implemented.

@k8s-ci-robot k8s-ci-robot removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 5, 2019
@fabriziopandini
Copy link
Member

/close
While i'm still convinced it is nice to have, currently there is no concrete use case for having those annotation. The ticket can always be re-opened/re-created if necessary

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: Closing this issue.

In response to this:

/close
While i'm still convinced it is nice to have, currently there is no concrete use case for having those annotation. The ticket can always be re-opened/re-created if necessary

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.

@neolit123
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/design Categorizes issue or PR as related to design. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

7 participants