Reconcile Cluster API Cloud Provider with the effort of moving Cloud Providers out of core K8s

[rsdcastro]

This issue is to track the discussion and whether or not those should be combined in some way.

cc @kris-nova @karan @roberthbailey

[rsdcastro]

Given potential implications to providers, tagging as something to be done for alpha if possible.

[roberthbailey]

What are the potential implications? Has there been a discussion about whether the efforts should be combined? Based on my knowledge of the cloud provider extraction, I think it's orthogonal to the cluster api development and we shouldn't tie ourselves to their timeline.

[rsdcastro]

As you can see from the description, this is to track the discussion - there has not been any discussions yet, but we need to have those. If they are orthogonal and we all agree on that, it should be documented in this issue or a separate doc. @cheftako

The implication I had in mind is any API change that might come out of that, but I could see other implications - like using a separate provider repository in a hypothetical scenario where the other cloud provider effort can fulfill the needs here.

[cheftako]

Also worth mentioning https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit#heading=h.w7i4ksrweimp which is main doc for the cloud provider working group.
Also https://github.com/kubernetes/community/blob/master/keps/0002-controller-manager.md is the relevant KEP.

[rsdcastro]

This issue was moved to kubernetes-sigs/cluster-api#39