Cluster-api: clusterctl pivots to internal cluster, make this optional

Created on 25 Jul 2018 · 6Comments · Source: kubernetes-sigs/cluster-api

In our use case we would like to use an external cluster other than minikube to deploy the cluster-api stack. This external cluster will manage multiple clusters. We would like to keep the controllers and cluster-api resources (machines, machineset, cluster, etc) on the external cluster.

The default behavior of clusterctl is to pivot the controllers and resources to the internal cluster. We would like to make the pivoting optional, @timothysc prefers that we do not pivot by default.

Source

oneilcin

👍2

Most helpful comment

Realized if clusterctl is used to deploy the managing cluster only, then the change is not needed for our use-case. The created cluster would be the managing cluster of other clusters. Then we could use kubectl or api calls to create the cluster and machines resources for adding new clusters.

oneilcin on 26 Jul 2018

👍2

All 6 comments

I would be glad to work on this

oneilcin on 25 Jul 2018

I would also prefer not to pivot by default.
It would actually be nice if we can inject kubeConfig of existing cluster where we keep the cluster-api stack and not necessarily depend on Minikube.

hardikdr on 26 Jul 2018

👍1

oneilcin on 26 Jul 2018

👍2

I'm planning on starting to look at this tomorrow.

detiber on 26 Jul 2018

Is this a specialization of the more general issue described in https://github.com/kubernetes-sigs/cluster-api/issues/479? Can we consolidate work around making the cluster creation pluggable?