@bsalamat I'm going to add this to the 1.15 milestone for tracking purposes. Once the KEP has been merged lets get the link updated. As usual, put any relevant k/k PRs to be tracked in this issue. Thanks!

/milestone v1.15
/stage alpha

/assign @Huang-Wei

@bsalamat, @Huang-Wei Kubernetes 1.15 Enhancement Freeze is 4/30/2019. To be included in the Kubernetes 1.15 milestone, KEPs are required to be 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.

@mrbobbytables thanks for the reminder.

@bsalamat I've raised #996 to address above concerns.

Hey, @Huang-Wei @bsalamat I'm the v1.15 docs release shadow.

I see that you are targeting the alpha version of 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! 😄

@Huang-Wei @bsalamat

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! 😄

@Huang-Wei @bsalamat. 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!

@Huang-Wei @bsalamat, 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.

/milestone clear

Hi @bsalamat @Huang-Wei , 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.

@kacole2 Yes, it's on the right track for 1.16, and it will be an Alpha feature.

@bsalamat @Huang-Wei

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!

@daminisatya It needs new docs. The doc PR (placeholder atm) has been created - kubernetes/website#15514

@savitharaghunathan I created a placeholder PR here kubernetes/website#18969

Hi @Huang-Wei, just a friendly reminder that the Code Freeze will go into effect on Thursday 5th March.

Can you please link all the k/k PRs or any other PRs which should be tracked for this enhancement?

Thank You :)

@palnabarun Here is an umbrella issue (kubernetes/kubernetes#87662) tracking the PRs. It progresses well right now - an e2e PR and a document PR need to be finished.

Thank you @Huang-Wei for the updates. It's great to see the progress. :)

@palnabarun All items to qualify this feature to be beta in 1.18 has been completed. Feel free to update the description of this issue.

Thanks @Huang-Wei for the efforts. 👏

I will update the issue comment.

/milestone clear

(removing this enhancement issue from the v1.18 milestone as the milestone is complete)

@palnabarun we'd like to promote it to GA in 1.19.

Hi @Huang-Wei, thank you for the update. We will update the tracking sheet accordingly. 👍

/stage stable
/milestone v1.19

#1796 is just adopting the new KEP template (with PRR).

Hey, @Huang-Wei @bsalamat I'm one of the v1.19 docs release shadows.

Could you please let me know if this piece of enhancement work planned requires any new docs (or modifications to existing docs) for 1.19 release?

If not, can you please update the 1.19 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.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

Regards,
Divya

@divya-mohan0209 kubernetes/website#21115 acts as a placeholder.

Hi @Huang-Wei Just to confirm: is this now code complete for 1.19 GA?

@kikisdeliveryservice yes, all code items have been completed - tracked at kubernetes/kubernetes#89433 (comment).

Hi @Huang-Wei !

Thanks for letting me know! This is mostly not applicable as your code is complete, but to follow-up on the email sent to k-dev today, I wanted to let you know that Code Freeze has been extended to Thursday, July 9th. You can see the revised schedule here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.19

Please let me know if you have any questions. 😄

Best,
Kirsten

Hi all

Enhancements Lead here. As this graduated to stable in 1.19 and the underlying KEP is marked implemented I am closing this issue.

Thank you for all of your work!!

Best,
Kirsten