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.

Sign up for GitHub

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

Jump to bottom

Add information on supported version skew and upgrade order #11060

Merged
merged 4 commits into from
Dec 8, 2018
Merged

Add information on supported version skew and upgrade order #11060

merged 4 commits into from
Dec 8, 2018

Conversation

liggitt
Copy link
Member

@liggitt liggitt commented Nov 18, 2018 •
edited

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:

  • it has implications for component upgrade order
  • it is necessary for cluster deployers to know what the skew guarantees are so they know what to deploy
  • it is necessary for component owners to know what skew they are expected to support so they know what cases to handle
  • it is important for reviewers to know what changes are acceptable to make in a given release

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:

references:

relevant owners for open questions:

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/network Categorizes an issue or PR as relevant to SIG Network. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. language/en Issues or PRs related to English language labels Nov 18, 2018
@k8sio-netlify-preview-bot
Copy link
Collaborator

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 563d289

https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com

@k8sio-netlify-preview-bot
Copy link
Collaborator

k8sio-netlify-preview-bot commented Nov 18, 2018 •
edited

Deploy preview for kubernetes-io-master-staging ready!

Built with commit fc6f306

https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com

@liggitt
Copy link
Member Author

liggitt commented Nov 18, 2018 •
edited

assigning representatives from the various tagged sigs/components. please review or nominate an alternate.

/assign @justaugustus
representing sig-release

/assign @timothysc
representing cluster-lifecycle

/assign @bgrant0607 @smarterclayton
representing sig-architecture

/assign @thockin
for kube-proxy upgrade order question

/assign @soltysh
for kubectl

/assign @lavalamp
for kube-apiserver / kube-controller-manager

/assign @derekwaynecarr
for kubelet

@liggitt liggitt mentioned this pull request Nov 18, 2018
Closed
2 tasks
neolit123
neolit123 approved these changes Nov 18, 2018
View reviewed changes
Copy link
Member

@neolit123 neolit123 left a 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
👍

content/en/docs/setup/version-skew-policy.md Outdated Show resolved Hide resolved
@spiffxp
Copy link
Member

spiffxp commented Dec 7, 2018

/unassign @timothysc
github only allows a max of 10 assignees per issue/pr, so I'm kicking off someone who already gave a +1 to make room for @mistyhacks

@spiffxp
Copy link
Member

spiffxp commented Dec 7, 2018

/assign @mistyhacks

@spiffxp spiffxp mentioned this pull request Dec 8, 2018
Closed
@mdlinville
Copy link
Contributor

/approve

I already did a review pass earlier, and we can iterate.

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 8, 2018
@k8s-ci-robot k8s-ci-robot merged commit 75ed07f into kubernetes:master Dec 8, 2018
@derekwaynecarr
Copy link
Member

noting this looked good for sig-node

@liggitt liggitt mentioned this pull request Dec 22, 2018
Closed
kychool pushed a commit to kychool/website that referenced this pull request Dec 26, 2018
@liggitt @kychool
Add information on supported version skew and upgrade order (kubernet…
deedb39 
…es#11060)

* Add information on supported version skew and upgrade order

* address comments

* added cloud-controller-manager

* format headers
kychool pushed a commit to kychool/website that referenced this pull request Dec 26, 2018
@liggitt @kychool
Add information on supported version skew and upgrade order (kubernet…
35ba9d1 
…es#11060)

* Add information on supported version skew and upgrade order

* address comments

* added cloud-controller-manager

* format headers
immutableT pushed a commit to immutableT/website that referenced this pull request Jan 9, 2019
@liggitt
Add information on supported version skew and upgrade order (kubernet…
14f17ae 
…es#11060)

* Add information on supported version skew and upgrade order

* address comments

* added cloud-controller-manager

* format headers
immutableT pushed a commit to immutableT/website that referenced this pull request Jan 9, 2019
@liggitt
Add information on supported version skew and upgrade order (kubernet…
a067cff 
…es#11060)

* Add information on supported version skew and upgrade order

* address comments

* added cloud-controller-manager

* format headers
@wenjiaswe wenjiaswe mentioned this pull request Jan 15, 2019
Closed
2 tasks
This was referenced Jan 22, 2019
Closed
Closed
Closed
Closed
Closed
Open
Closed
Open
@liggitt
Copy link
Member Author

liggitt commented Jan 22, 2019

opened follow-up issues to track individual items and created an umbrella issue at #12329

bsalamat pushed a commit to bsalamat/kubernetes.github.io that referenced this pull request Jan 29, 2019
@liggitt @bsalamat
Add information on supported version skew and upgrade order (kubernet…
df54487 
…es#11060)

* Add information on supported version skew and upgrade order

* address comments

* added cloud-controller-manager

* format headers
@tpepper
Copy link
Member

tpepper commented Mar 15, 2019

/wg lts

@k8s-ci-robot k8s-ci-robot added the wg/lts Categorizes an issue or PR as relevant to WG LTS. label Mar 15, 2019
@tpepper tpepper added this to Done in WG LTS Mar 15, 2019
@liggitt liggitt mentioned this pull request Nov 9, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@spiffxp spiffxp spiffxp left review comments

@timothysc timothysc timothysc left review comments

@neolit123 neolit123 neolit123 approved these changes

@lavalamp lavalamp lavalamp left review comments

@sttts sttts sttts left review comments

@tpepper tpepper tpepper left review comments

@fabriziopandini fabriziopandini fabriziopandini left review comments

@mdlinville mdlinville mdlinville left review comments

@bgrant0607 bgrant0607 bgrant0607 left review comments

@roberthbailey roberthbailey roberthbailey left review comments

@yastij yastij yastij left review comments

@yue9944882 yue9944882 yue9944882 left review comments

@andrewsykim andrewsykim andrewsykim left review comments

@k82cn k82cn k82cn left review comments

@nikopen nikopen nikopen left review comments

@soltysh soltysh soltysh approved these changes

@Rajakavitha1 Rajakavitha1 Awaiting requested review from Rajakavitha1

Assignees

@justaugustus justaugustus

@soltysh soltysh

@lavalamp lavalamp

@calebamiles calebamiles

@smarterclayton smarterclayton

@tpepper tpepper

@thockin thockin

@derekwaynecarr derekwaynecarr

@mdlinville mdlinville

@bgrant0607 bgrant0607

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
WG LTS
  
Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Document supported component skew