/sig node
/milestone v1.15
/assign

/sig scheduling

@tallclair Does /assign means you'd like to cover the implementation?

@Huang-Wei - I was planning to work on this, as per discussion with @tallclair and kubernetes/kubernetes#72413

Cool, I recalled you mentioned that.

@tallclair i'm going to add this to the tracking sheet for Kubernetes 1.15. I've updated your OP with a direct link to the KEP as well. As usual, please add links to all k/k PRs in this issue so code can be tracked properly. Thanks!

ref kubernetes/kubernetes#75744

Hey, @tallclair I'm the v1.15 docs release shadow.

I see that you are targeting this enhancement for the 1.15 release. Does this require any new docs (or modifications)?

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! 😄

Yes, I will open a doc update (addition to the runtime class page), assuming this makes the cut.

Thank you @tallclair

Please do share the link to the draft docs PR over here or ref to this issue so that I can track it.

Hi @tallclair . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

Hi, @yastij I am docs Lead here!
Will this enhancement need docs?

/milestone clear

Hi @yastij @tallclair , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

The plan is to add this to 1.16, but tie it's status to RuntimeClass. In other words, reuse the runtimeclass feature gate, and make it beta.

@yastij @tallclair

I'm one of the v1.16 docs shadows.
Does this enhancement (or the work planned for v1.16) require any new docs (or modifications to existing docs)? If not, can you please update the 1.16 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.16) due by Friday, August 23rd, it can just be a placeholder PR at this time. Let me know if you have any questions!

Any update on docs?

Yeah, this should have a docs update. I'll send a PR next week.

Docs PR: kubernetes/website#15989

@tallclair code freeze for 1.16 is on Thursday 8/29. Are there any outstanding k/k PRs that still need to be merged for this to go Beta?

Yes, see kubernetes/kubernetes#81016

All the PRs related to RuntimeClass Scheduling except the doc kubernetes/kubernetes#81016 have already been merged into the master branch.

All the PRs required in the beta release have been merged. 🎉

Hey there @draveness @tallclair @yastij -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable 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, please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

/milestone clear

I don't have any runtimeclass scheduling changes planned for v1.17. I would like to let feature soak for another release before graduating to GA.

Note that this is tied to the RuntimeClass feature, and will graduate with it (maybe in v1.18).

Noted -- thanks for the update!

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

/remove-lifecycle stale

Hey there @tallclair -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha|beta|stable in 1.18?

The current release schedule is:
Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.
If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

The lifecycle for this feature should now be tied to RuntimeClass (#585), and no longer needs to be tracked separately.

/close

@tallclair: Closing this issue.