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

Jump to bottom

Increase Kubernetes support window to one year #1498

Closed
youngnick opened this issue Jan 22, 2020 · 33 comments
Closed

Increase Kubernetes support window to one year #1498

youngnick opened this issue Jan 22, 2020 · 33 comments
Labels
kind/design Categorizes issue or PR as related to design. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
[RETIRED] SIG PM

Comments

@youngnick
Copy link
Contributor

youngnick commented Jan 22, 2020 •
edited

Enhancement Description

  • One-line enhancement description (can be used as a release note): The Kubernetes support window has been released to one year, or four releases. This is a change from nine months, or three releases.
  • Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR) Add Kubernetes Yearly Support Period KEP #1497
  • Primary contact (assignee): @youngnick
  • Responsible SIGs: wg-lts
  • Enhancement target (which target equals to which milestone):
    • Stable release target (1.181.19)

This KEP and proposal involve increasing the support window from three releases to four, as recommended by WG-LTS. This is an effort that will span a lot of SIGs, with SIG-Architecture, SIG-Release, and SIG-Testing being the most impacted.

It does not require code changes, and is a process change.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 22, 2020
@youngnick
Copy link
Contributor Author

/wg wg-lts
/sig sig-architecture
/sig sig-release
/sig sig-testing

@k8s-ci-robot
Copy link
Contributor

@youngnick: The label(s) wg/wg-lts, sig/sig-architecture, sig/sig-release, sig/sig-testing cannot be applied, because the repository doesn't have them

In response to this:

/wg wg-lts
/sig sig-architecture
/sig sig-release
/sig sig-testing

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.

@youngnick
Copy link
Contributor Author

OK then.

@youngnick
Copy link
Contributor Author

/wg wg-lts

@k8s-ci-robot
Copy link
Contributor

@youngnick: The label(s) wg/wg-lts cannot be applied, because the repository doesn't have them

In response to this:

/wg wg-lts

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

/wg lts
/sig architecture
/sig release
/sig testing

@k8s-ci-robot k8s-ci-robot added wg/lts Categorizes an issue or PR as relevant to WG LTS. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 22, 2020
@neolit123 neolit123 added the kind/design Categorizes issue or PR as related to design. label Jan 22, 2020
@justaugustus justaugustus added this to Backlog in [RETIRED] SIG PM via automation Jan 23, 2020
@justaugustus justaugustus added this to Backlog in Release Team via automation Jan 23, 2020
@justaugustus justaugustus added this to Backlog in SIG Release via automation Jan 23, 2020
@justaugustus justaugustus added this to the v1.19 milestone Jan 23, 2020
@justaugustus
Copy link
Member

@youngnick -- We'll need to open this for discussion across mailing lists AND achieve consensus on this across all of the stakeholder SIGs and I do not see that happening by Enhancements Freeze or 1.18.

See the Slack convo happening here: https://kubernetes.slack.com/archives/C2C40FMNF/p1579736459090100

@cblecker
Copy link
Member

-1 for targeting 1.18. See my comment here: #1497 (review)

@BenTheElder
Copy link
Member

BenTheElder commented Jan 23, 2020 •
edited

[noting that enhancements freeze is tuesday, review + buy-in from affected sigs (... all of them?) does seem unlikely by then 😅 ]

@jeremyrickard jeremyrickard added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 23, 2020
@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 Apr 27, 2020
@youngnick
Copy link
Contributor Author

The discussion on this one has been happening on #1497 instead of here.

@youngnick
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2020
@xmudrii xmudrii mentioned this issue May 11, 2020
Closed
7 tasks
@palnabarun palnabarun added tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 14, 2020
@palnabarun
Copy link
Member

palnabarun commented May 15, 2020 •
edited

After a discussion with Tim on Slack, adding the enhancement to the tracking sheet and setting the graduation stage as stable.

A point to note here is this enhancement does not follow the conventional graduation style of Alpha -> Beta -> Stable but is either implemented in a release cycle or not. Hence, marking it as stable.

/stage stable

cc: @tpepper

@palnabarun
Copy link
Member

@youngnick @tpepper @justaugustus -- I saw that an exception request was filed for this enhancement due to the lazy consensus period. Till the exception gets accepted, removing the Enhancement from the milestone.

Thanks for the proactive exception request. 👍

@palnabarun palnabarun added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 20, 2020
@palnabarun
Copy link
Member

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.19 milestone May 20, 2020
@palnabarun
Copy link
Member

@youngnick @tpepper @justaugustus -- The exception request was approved. Adding this enhancement back to the milesone.

/milestone v1.19

@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone May 25, 2020
@palnabarun palnabarun added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 25, 2020
@savitharaghunathan
Copy link
Member

Hi @youngnick - I am Savitha,1.19 Docs lead. Does this enhancement work planned for 1.19 require any new docs (or modifications to existing docs)? If not, can you please update the 1.19 Enhancement Tracker Sheet, or let me know, I can do it for you :)
If docs are required, just a friendly reminder that we are looking for a PR against k/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

@youngnick
Copy link
Contributor Author

It will need some modifications to the docs about support windows at least, so I'll say yes. @tpepper may have more here.

I'll work on sorting out the docs PR as soon as I can.

@savitharaghunathan
Copy link
Member

Hi @youngnick, Just a reminder that docs placeholder PR against dev-1.19 is due by June 12th. Once you have it in place, can you update this issue with a link to the PR?

If you already have a placeholder PR against dev-1.19 branch, please provide the link here. Thanks!

@krmayankk
Copy link

Does this apply to major version or minor versions ?

@tpepper
Copy link
Member

tpepper commented Jun 9, 2020

Does this apply to major version or minor versions ?

We're talking about the delivery of patch versions for minor versions. Across this discussion the major version has always been only "1", which may make things confusing. If/when someday the major version moves to "2", we will have to decide as a project if we keep some patching happening on a 1.X branch also.

@tpepper
Copy link
Member

tpepper commented Jun 11, 2020

@savitharaghunathan we've been discussing multiple points of potential docs updates and will get hopefully a non-placeholder but rather initial actual Docs PR open on this at the beginning of next week, based on the understanding from the Jun 8, 2020 release 1.19 team meeting intent to shift the coming deadlines out a week or so.

@savitharaghunathan
Copy link
Member

savitharaghunathan commented Jun 11, 2020 •
edited

@tpepper thanks for the update. Sounds good to me :)

Thanks to @youngnick for updating me about the status :)

@savitharaghunathan
Copy link
Member

Hi @youngnick, @tpepper: Friendly reminder: Placeholder PR deadline has been extended to June 19th. Just checking in to see if there is any update. Thanks!

@tpepper
Copy link
Member

tpepper commented Jun 17, 2020

PR coming

@tpepper
Copy link
Member

tpepper commented Jun 20, 2020

@savitharaghunathan here's a number of documentation PRs relative to this KEP:

kubernetes/sig-release#1121
kubernetes/community#4872
kubernetes/website#21928

@kikisdeliveryservice
Copy link
Member

Hi @tpepper @youngnick !

Enhancements Lead here. Can you confirm that this was stable in 1.19? If so can you please update the KEP's status to implemented and close this issue once that merges?

Thanks!
Kirsten

@kikisdeliveryservice kikisdeliveryservice removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 11, 2020
@tpepper
Copy link
Member

tpepper commented Sep 14, 2020

#1986

@youngnick
Copy link
Contributor Author

This one is all done.

SIG Release automation moved this from Backlog to Done (1.19) Sep 17, 2020
Release Team automation moved this from Backlog to Done (1.20) Sep 17, 2020
@kikisdeliveryservice
Copy link
Member

Thanks all!!!

@kikisdeliveryservice
Copy link
Member

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.19 milestone Sep 17, 2020
@justaugustus justaugustus mentioned this issue Feb 10, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/design Categorizes issue or PR as related to design. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
No open projects
[RETIRED] SIG PM
Backlog
Milestone
No milestone
Development

No branches or pull requests