Support Out-of-Tree CloudStack Cloud Provider

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Support Out-of-Tree CloudStack Cloud Provider by running the cloud-controller-manager
• Primary contact (assignee):
  @andrewsykim
• Responsible SIGs:
  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:
  @andrewsykim
• Approver (likely from SIG/area to which enhancement belongs):
  @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 cloud-provider

[andrewsykim]

@ngtuna @sebgoa @svanharmelen are any of you available to take this?

[svanharmelen]

@andrewsykim I left the company that used both Kubernetes and CloudStack about 8 months ago and currently don't use either of them on a regular basis anymore. So unfortunately I will not be able to help out here.

[sebgoa]

same here. This needs to be picked up by an active community member like @rhtyd

[andrewsykim]

Don't think this issue will be alpha in v1.14.

[justaugustus]

/assign @andrewsykim

[justaugustus]

/assign @rhtyd

[k8s-ci-robot]

@justaugustus: GitHub didn't allow me to assign the following users: rhtyd.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @rhtyd

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[evillgenius75]

Hi @andrew, 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.

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

I notice there is no KEP for this Enhancement. 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.

[rohityadavcloud]

We're aware of at least two CloudStack controller managers (ccms) developed by CloudStack users/contributors:
https://github.com/swisstxt/cloudstack-cloud-controller-manager (cc @onitake @joschi36)
https://github.com/tsuru/custom-cloudstack-ccm (cc @andrestc @cezarsa)

It's possible we integrate in-built kubernetes support in CloudStack (via kubeadm and custom systemvmtemplate etc) in near future versions, in which case the controller can be part of CloudStack codebase and its setup and orchestration will be managed by CloudStack as part of the k8s cluster setup and lifecycle management.

[onitake]

@rhtyd We'll gladly transfer ownership of swisstxt/cloudstack-cloud-controller-manager to the Apache/CloudStack project if you decide to accept it.

We still have a few issues that weren't anticipated when we factored the CCM out of KCM, but they should definitely be fixed to make the controller production-ready for most users. Other than that, we're using it productively in-house very successfully, so I think it would be a good addition.

[rohityadavcloud]

Thanks @onitake I'll start a discussion thread on dev@ ML and mention your intent.

[rohityadavcloud]

FYI I've started a discussion on CloudStack dev mailing list and request this repository: https://github.com/apache/cloudstack-kubernetes-provider