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

clarify patch/minor version upgrade process #12324

Closed
1 task
Tracked by #12329
liggitt opened this issue Jan 22, 2019 · 14 comments · Fixed by #35574
Closed
1 task
Tracked by #12329

clarify patch/minor version upgrade process #12324

liggitt opened this issue Jan 22, 2019 · 14 comments · Fixed by #35574
Assignees
@timothysc @imkin @luxas @roberthbailey
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. 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. triage/accepted Indicates an issue or PR is ready to be actively worked on. wg/lts Categorizes an issue or PR as relevant to WG LTS.

Comments

@liggitt
Copy link
Member

liggitt commented Jan 22, 2019 •
edited
Loading

Follow up from #11060, tracked in #12329

Tested/supported upgrade process for patch releases and minor releases is not clear in user-facing documentation:

  • should we add requirements (or at least a strong recommendation) to be at latest patch version of 1.x prior to upgrades, and upgrade to latest patch version of 1.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-reviews @kubernetes/sig-testing

Page to Update:
https://kubernetes.io/docs/setup/version-skew-policy/
@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. labels Jan 22, 2019
This was referenced Jan 22, 2019
Merged
Open
@fabriziopandini
Copy link
Member

+1 for adding strong raccomdation to be at latest patch version of 1.x prior to upgrades, and upgrade to latest patch version of 1.x+1

@neolit123
Copy link
Member

neolit123 commented Feb 5, 2019 •
edited
Loading

/assign @timothysc @luxas @roberthbailey
sig-cluster-lifecycle: hello, we need feedback and approval for the proposals in this ticket from chairs with respect to LTS.

@roberthbailey
Copy link
Contributor

I think a strong recommendation is ok; I don't think there should be a requirement. In some cases a provider may want to jump consumers between specific versions for upgrades that have been well tested, and if we make it a requirement to pick the latest patch version that may actually make it more difficult to qualify and upgrade clusters (because the qualification would reset each time a patch was cut).

@imkin
Copy link

imkin 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
@imkin
Copy link

imkin commented Apr 23, 2019

Should this be based on the existing upgrade tests we have?

/assign

@sftim
Copy link
Contributor

sftim commented Jun 4, 2019

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jun 4, 2019
@sftim sftim mentioned this issue Jun 24, 2019
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/kind feature
/priority backlog

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Sep 10, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 10, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

@liggitt
Copy link
Member Author

liggitt commented Jun 26, 2020

/reopen
/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot reopened this Jun 26, 2020
@k8s-ci-robot
Copy link
Contributor

@liggitt: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

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.

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jun 26, 2020
@sftim
Copy link
Contributor

sftim commented Oct 8, 2020

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Oct 8, 2020
@shannonxtreme shannonxtreme mentioned this issue Jul 30, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@timothysc timothysc

@imkin imkin

@luxas luxas

@roberthbailey roberthbailey

Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. 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. triage/accepted Indicates an issue or PR is ready to be actively worked on. wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add recommendation to use most recent patch versions of minors shannonxtreme/website
10 participants
@timothysc @neolit123 @liggitt @imkin @fabriziopandini @luxas @roberthbailey @k8s-ci-robot @sftim @fejta-bot