Fixes kubernetes/kubernetes#65435

@apelisse --

It looks like this feature is currently in the Kubernetes 1.12 Milestone.

If that is still accurate, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38
/kind feature
/stage alpha

@justaugustus I think we're good!

Thanks for the update, @apelisse!

Hey there! @apelisse I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

Design proposal link is invalid. Looks like it has moved to https://github.com/kubernetes/community/blob/master/keps/sig-api-machinery/0015-dry-run.md.

@phillipao -- thanks for pointing that out! I've updated the link in the description. :)

@apelisse @jennybuckley --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).

cc: @zparnold @jimangel @tfogo

Still on track, fixing and pushing the doc PR (kubernetes/website#10033), thanks for the ping!

Thanks for the update, @apelisse !

This will fix kubernetes/kubernetes#11488.

Also fixes kubernetes/kubernetes#62197

/stage beta

@apelisse @deads2k @lavalamp what work needs to be done to move this to beta? are there any issues or PR's we can link to track this?

🤦‍♂️ right, I just noticed kubernetes/kubernetes#68514 but since one of those items is Beta/GA I can't tell if this is just "make docs look good" or if there is code that needs to be written for this

Yeah, the Beta/GA means that it'd be nice if we have it for beta, not mandatory. So it's basically just docs I think.

Enhancement issues opened in kubernetes/enhancements should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.

/remove-lifecycle frozen

Hey there @apelisse -- 1.17 Enhancements shadow here 👋 . I wanted to check in and see if you think this Enhancement will be graduating to 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, I'll add it to the 1.17 tracking sheet (https://bit.ly/k8s117-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

We are planning on promoting this feature to GA in 1.18.

@apelisse thanks Antoine, I will add it to 1.18 release tracking

/milestone v1.18

Updated the issue description to the correct KEP.

Looks like the KEP here was missing some section, we just merged #1535 to address the problem. Thanks

Thank you @apelisse for addressing this. :)

This received an exception to enhancement freeze.

Hello, @apelisse - I'm a Docs shadow on the 1.18 release team.

Does this enhancement work planned for 1.18 require any new docs or modifications to existing docs?

If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)

If doc updates are required, reminder that the placeholder PRs against k/website (branch dev-1.18) are due by Friday, Feb 28th.

Let me know if you have any questions!

Thanks for the reminder, we're already actively working on documentation for this feature. @zhouya0

Hi @apelisse, code freeze is March 5. Please list out/link to any PRs you are working on toward this enhancement, so we can track it in the release team. Thanks!

That PR is the last piece of work that needs to go in before code-freeze, thanks!

Hi @apelisse
We are close to the docs placeholder PR deadline against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhancements much better.
Could you please share the link to docs placeholder PR?

Thanks! :)

I've created the empty PR: kubernetes/website#19287

#1628