/milestone v1.15
/stage stable

/assign @ravisantoshgudimetla

@ravisantoshgudimetla, Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be merged and in an "Implementable" state with proper test plans and graduation criteria. Please submit any PRs needed to make this KEP adhere to inclusion criteria. If this will slip from the 1.15 milestone, please let us know so we can make appropriate tracking changes.

Thanks @craiglpeters - To be clear, what's an "implementable" state? some WIP PR?

@ravisantoshgudimetla The current KEP listed above is not following the correct procedure. For any new enhancement or feature to Kubernetes a KEP must be filed, accepted, and merged by a particular SIG that will review it. I don't see the process has been followed here. Please review this at the root of this rep. https://github.com/kubernetes/enhancements

For now, this feature is going to be untracked and removed from the 1.15 milestone

/milestone clear

@kacole2, here is the KEP created for it, I did not update this issue with KEP. Please let me know, if I need to do anything additional.

#987

/milestone v1.15

Hey @ravisantoshgudimetla I'm the v1.15 docs shadow.

Does this enhancement 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 Friday, May 31st. 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!

Hi @ravisantoshgudimetla . 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!

Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Friday, May 31st. 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!

I will get started on this.

Hi @ravisantoshgudimetla . 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.

Except for docs PR, the main PR is in review(which I believe should be merged by Thursday). I will get started on a docs PR.

HI @ravisantoshgudimetla docs PR does not have to be complete... The Today deadline needs to have a just a placeholder PR with title and description. Nothing fancy. This is mandatory before code freeze.

Hi @ravisantoshgudimetla, today is code freeze for the 1.15 release cycle. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

@craiglpeters - I don't have enough reviewers atm to review the PR. Is there a way to file exception?

Here is the PR: kubernetes/kubernetes#76310. It's so close yet so far :).

/milestone clear

Hi @ravisantoshgudimetla , 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.

/assign

Hello @draveness @ravisantoshgudimetla , 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?


Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

• 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

• A Kubernetes Enhancement Proposal (KEP) must meet the following criteria before Enhancement Freeze to be accepted into the release

  • PR is merged in
  • In an implementable state
  • Include test plan and graduation criteria

• All relevant k/k PRs should be listed in this issue

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

This feature has already graduated to GA, and we could close this now.

/close

@draveness: Closing this issue.

Hi @draveness, since this enhancement already graduated to Stable, can you please also mark the KEP as implemented?

/reopen
(reopening in the interim till the KEP in marked implemented)

@palnabarun: Reopened this issue.

/reopen
(reopening in the interim till the KEP in marked implemented)

Thanks for the reminder, I've opened a PR to updates the KEP.

/close
since #1700 has been merged

@draveness: Closing this issue.

@draveness -- Thank you for updating the KEP. 🙂