Support Out-of-Tree vSphere Cloud Provider

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Support Out-of-Tree vSphere Cloud Provider by running the cloud-controller-manager
• KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20190125-out-of-tree-vsphere.md
• Primary contact (assignee):
  @frapposelli @cantbewong
• Responsible SIGs:
  SIG VMware, SIG Cloud Provider
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  @frapposelli @cantbewong @andrewsykim
• Approver (likely from SIG/area to which enhancement belongs):
  @frapposelli @cantbewong @andrewsykim
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.14)
  • Beta release target (x.y)
  • Stable release target (x.y)

Ref #88

/sig vmware cloud-provider

[frapposelli]

/milestone v1.14
/stage beta

[andrewsykim]

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

[claurence]

@frapposelli @cantbewong 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

[frapposelli]

@claurence exception filed, KEP is in review as #767

[claurence]

exception approved - adding this back to the 1.14 milestone

[frapposelli]

@claurence PR #767 and #787 merged, we should be GTG.

[ameukam]

/label tracked/yes

[npentrel]

Hey @cantbewong @frapposelli 👋! I'm a v1.14 docs release 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.14) due by Friday, March 1. 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!

[ameukam]

Hello @frapposelli, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks

[frapposelli]

@ameukam @npentrel we should be good both on the PR and Docs front for this one, thanks!

[npentrel]

Just to confirm @frapposelli, you are saying this does not require docs changes?

[kacole2]

Hello @frapposelli , 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.

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

/milestone clear

[justaugustus]

/assign @frapposelli @cantbewong

[evillgenius75]

Hi @frapposelli @cantbewong, I'm a 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. If not's graduating, The current milestone will be clear and the tracking status will be tracked/no.

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.

[annajung]

Hello @frapposelli @cantbewong , 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

[fejta-bot]

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

[palnabarun]

/remove-lifecycle stale

[frapposelli]

/stage stable
/milestone v1.18

[johnbelamaric]

@frapposelli Release team enhancements shadow here. It looks like this is planned for 1.18, I will add it to the spreadsheet.

[johnbelamaric]

@frapposelli if you plan to got to stable, can we get some better graduation criteria? All it says now is that the criteria is that it is "complete". I guess that means "feature parity with in-tree". What about removal of in-tree? Can you clarify please?

[irvifa]

Hello @frapposelli @cantbewong I'm one of the v1.18 docs shadows.
Does this enhancement for (or the work planned for v1.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 so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th., it can just be a placeholder PR at this time. Let me know if you have any questions!

[frapposelli]

@johnbelamaric the out of tree provider for vSphere is feature complete and has feature parity with in-tree.

Removal of in-tree providers is tracked as a larger item by the extraction workgroup under SIG cloud provider. Currently all cloud providers are staged under legacy-cloud-providers in k/k, the plan of record is to remove all them at once in Kubernetes 1.21.

[irvifa]

@frapposelli Could you please create a placeholder PR to dev-1.18 for the documentation? Thanks!

[johnbelamaric]

@frapposelli Ok, thanks. So, the only thing left are docs?

[irvifa]

Hello @frapposelli I'm one of the v1.18 docs shadows.

Does this enhancement for (or the work planned for v1.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 so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, which is roughly 1 weeks from now. It can just be a placeholder PR at this time. Let me know if you have any questions!

[johnbelamaric]

Hi @frapposelli, since this is now complete, can you please mark the KEP as implemented and mark that PR as fixing this issue (closing the issue)? Thanks!

[palnabarun]

@frapposelli Ping. Can you please mark the corresponding KEP as implemented? 🙂