Support Out-of-Tree OpenStack Cloud Provider

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Support Out-of-Tree OpenStack Cloud Provider by running the cloud-controller-manager
• Primary contact (assignee):
  @dims @hogepodge
• Responsible SIGs:
  SIG OpenStack, 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:
  @dims @hogepodge @andrewsykim
• Approver (likely from SIG/area to which enhancement belongs):
  @dims @hogepodge @andrewsykim
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Ref #88

/sig openstack cloud-provider

[hogepodge]

/assign @hogepodge

[andrewsykim]

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

[hogepodge]

/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.

[andrewsykim]

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

[claurence]

@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

[kacole2]

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.

[hogepodge]

@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

[evillgenius75]

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.