/sig architecture
/sig testing
/sig network
/sig node

@kubernetes/sig-cluster-lifecycle
cc @luxas @justinsb @neolit123 @fabriziopandini

Would like to get an exception for 1.16, trying to get approval on the KEP (Jordan and Justin were primary reviewers, Derek helped take a look from sig-node). Will follow up early next week.

Hey there @smarterclayton , 1.17 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.17?

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do, I'll add it to the 1.17 tracking sheet (https://bit.ly/k8s117-enhancement-tracking). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

Yes, this will be alpha in 1.17.

KEP is updated with plan starting as alpha in 1.17

Thank you for the swift response. :)

Added this to 1.17 release.

/stage alpha
/milestone v1.17

Just FYI, all enhancements should have a KEP, the KEP PR should be merged, the KEP should be in an implementable state, have a testing plan and graduation criteria.

I see that you have updated your KEP with #1268. Please make sure that it is merged before the Enhancements Freeze.

Hello, @smarterclayton I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Hello @smarterclayton,

Please let us know if this enhancement requires docs. If so, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (4 more days left)

Hi @smarterclayton

I am one of the Enhancements Shadow for the 1.17 Release Team. We are very near to the Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. I see that kubernetes/kubernetes#80238 was filed in relation to this. Is there any other PR related to this enhancement? If yes, can you please link them here?

Thank you in advance 😄

@smarterclayton Thank you for the updates. :)

Hey there @smarterclayton , 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to beta in 1.18?

The current release schedule is:

Monday, January 6 - Release Cycle Began
Tuesday, January 28, EOD PST - Enhancements Freeze
Thursday, March 5, EOD PST - Code Freeze
Monday, March 16- Docs must be completed and reviewed
Tuesday, March 24 - Kubernetes 1.18.0 Released

If you do, I'll add it to the 1.17 tracking sheet (http://bit.ly/k8s-1-18-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

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

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-contributor-experience at kubernetes/community.
/close

@fejta-bot: Closing this issue.

/remove-lifecycle rotten
/reopen
kubernetes/kubernetes#100776 will fix it in 1.22

@pacoxu: Reopened this issue.

/assign @ehashman @dims @neolit123 @spiffxp
assigning to arbitrary chairs from each of the labeled SIGs... is this something that we are actively planning to tackle for v1.22?

Like, I don't know enough about this to know what needs to happen beyond "land kubernetes/kubernetes#100776".

I also don't know if this is at a state where it's already been announced in a changelog, GA'ed, and we just forgot to clean stuff up?

kubernetes/kubernetes#100776 is the only remaining action, according to the KEP.

Release 5 (1.22):
The LegacyNodeRoleBehavior gate and all feature-level gates are removed, components that attempt to set these gates will fail to start.
Code that references node-roles within Kubernetes will be removed.

In Release 5 (which could be as early as 1.21) this KEP will be considered complete.

https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1143-node-role-labels#migrating-existing-deployments

/assign @ehashman @dims @neolit123 @spiffxp
assigning to arbitrary chairs from each of the labeled SIGs... is this something that we are actively planning to tackle for v1.22?

I am not a chair of one of the labelled SIGs.

/cc @liggitt
who I think know more about where this is at

+1 to land kubernetes/kubernetes#100776 and close this up in 1.22.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

+1 to land kubernetes/kubernetes#100776 and close this up in 1.22.

kubernetes/kubernetes#100776 landed, shall we close then?

I think we can close this now.
Please reopen if needed.