/assign @hogepodge

@hogepodge can you assign a stage target for v1.14?

/stage alpha

KEP to be sent up soon to enumerate graduation criteria. We have a stable external provider, but need to engage with the release process to move this to officially stable.

FYI put together the boiler plate for this KEP here #735

@dims @hogepodge since the KEP for this issue hasn't been merged yet we will be removing it from the 1.14 milestone. To have it added back in please file an exception - information on the exception process can be found here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

Hello @hogepodge , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. Please attach a KEP to the original post as well.

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

@kacole2 I'll follow up with the team tomorrow. We should definitely be able to say we're on stable since we've been running the out of tree provider for more than a year now, and encouraging users to adopt that rather than use the in-tree provider.

cc @adisky

Hi @hogepodge @andrewsykim , I'm the 1.16 Enhancement Shadow. 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.

I see the KEP is still under provisional state, as a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

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

Thank you.

Hey there @hogepodge, 1.17 Enhancements shadow 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, 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!

I'm no longer running the project, but the external provider is stable and in wide usage. Adding @adisky who is the new point of contact.

/assign @adisky

Thanks for the updates. :)

@adisky It looks like you have a WIP KEP PR, is this something you'd like tracked for 1.17? If so, the KEP must be merged meet the following criteria:

• in an implementable state
• Have a test plan
• Have graduation criteria

If you could ack back soon if possible, it'd be greatly appreciated 👍

Thanks!

/unassign hogepodge
(from earlier comment)

@mrbobbytables it is implemented long back, testing is also done, have graduation criteria too, it is WIP as some fields are TODO's

@adisky -- Unfortunately the deadline for the 1.17 Enhancement freeze has passed and the KEP is still not merged. For now, this is being removed from the milestone and 1.17 tracking sheet. If there is a need to get this in, please file an enhancement exception.

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

@adisky the KEP is still showing status provisional, even after #1303 merged. Can you update it to implemented if everything is done, and close this issue?

Or, is there still work to be done, such as removing the in-tree provider?

@johnbelamaric the work for removing intree provider is still remaining.

Is that part of this KEP or will it be done as part of https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20190125-removing-in-tree-providers.md ?

If it's not needed to say that this KEP is "done", and there is no additional work needed for this KEP (it is fully completed) then you would:

1. go into the actual KEP file and create a PR that sets the header status to implemented, and updates the implementation history.
2. Mark that it fixes this issue

When that merges it should close this issue.

cc @ramineni would you be able to create a PR for marking this KEP as implemented?

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

This feature is complete and the KEP marked implemented. Any remaining work to remove the in-tree provider is tracked under a different feature.

/close

@johnbelamaric: Closing this issue.

/milestone v1.17

(since the enhancement was completed in that cycle)