-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 information on supported version skew and upgrade order #11060
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit 563d289 https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com |
Deploy preview for kubernetes-io-master-staging ready! Built with commit fc6f306 https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com |
assigning representatives from the various tagged sigs/components. please review or nominate an alternate. /assign @justaugustus /assign @timothysc /assign @bgrant0607 @smarterclayton /assign @thockin /assign @soltysh /assign @lavalamp /assign @derekwaynecarr |
1237fe4
to
5f7af58
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.
thanks a lot for this write up @liggitt
👍
/unassign @timothysc |
/assign @mistyhacks |
/approve I already did a review pass earlier, and we can iterate. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgrant0607, mistyhacks The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
noting this looked good for sig-node |
…es#11060) * Add information on supported version skew and upgrade order * address comments * added cloud-controller-manager * format headers
…es#11060) * Add information on supported version skew and upgrade order * address comments * added cloud-controller-manager * format headers
…es#11060) * Add information on supported version skew and upgrade order * address comments * added cloud-controller-manager * format headers
…es#11060) * Add information on supported version skew and upgrade order * address comments * added cloud-controller-manager * format headers
opened follow-up issues to track individual items and created an umbrella issue at #12329 |
…es#11060) * Add information on supported version skew and upgrade order * address comments * added cloud-controller-manager * format headers
/wg lts |
Fixes #7103
Preview available at: https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com/docs/setup/version-skew-policy/
We have a document that details the deprecation policy for APIs, but no document on the website detailing supported versions and version skew between Kubernetes components.
This is important information to make clear, for many reasons:
This PR attempts to clarify the currently supported state of supported Kubernetes versions and component version skew.
I'd like to resolve the following questions, get feedback from various sigs, and merge this around the time 1.13 releases (and mention it in the release notes), currently targeted for 12/3.
follow-up discussion topics/updates:
what version skew does the- clarify kube-proxy skew support and upgrade process #12322kube-proxy
component support relative to the apiserver and kubelet? @kubernetes/sig-network-pr-reviewsis a specific upgrade order between- clarify kube-proxy skew support and upgrade process #12322kube-proxy
andkubelet
required? @kubernetes/sig-network-pr-reviews, @kubernetes/sig-node-pr-reviewsis a specific upgrade order between- clarify kube-controller-manager/kube-scheduler skew support and upgrade order #12323kube-controller-manager
andkube-scheduler
required? @kubernetes/sig-api-machinery-pr-reviews, @kubernetes/sig-scheduling-pr-reviewsshould we add requirements (or at least a strong recommendation) to be at latest patch version of- clarify patch/minor version upgrade process #123241.x
prior to upgrades, and upgrade to latest patch version of1.x+1
(since that is what we test, and what we can fix if broken)? @kubernetes/sig-architecture-pr-reviews @kubernetes/sig-release @kubernetes/sig-cluster-lifecycle-pr-reviewsadd details to kubelet upgrade procedure (whether drain is required, whether skip-level kubelet upgrades are supported, etc) @kubernetes/sig-node-pr-reviews @kubernetes/sig-storage-pr-reviews- clarify kubelet upgrade process #12326what statement should be made about new features in version 1.x when running with a 1.x+ control plane and kubelets older than 1.x? is the user responsible for labeling nodes and workloads to only steer pods using those features to nodes with those capabilities? @kubernetes/sig-node-pr-reviews @kubernetes/sig-architecture-pr-reviews- clarify support of new features across version-skewed clusters #12325control plane downgrade (and safe rollback in rolling HA upgrade) (Add information on supported version skew and upgrade order #11060 (comment), Add information on supported version skew and upgrade order #11060 (comment), Add information on supported version skew and upgrade order #11060 (comment))- clarify control plane downgrade and/or rollback during HA upgrade #12327what is our stated support or testing for transitive or third-party dependencies?- clarify tested/supported versions of transitive or third-party dependencies #12328references:
relevant owners for open questions: