Cluster-api: [Document] How to provision a k8s cluster with an existing k8s cluster but not bootstrap cluster?

[gyliu513]

I found that the k8s provision with openstack can either use a bootstrap cluster or use an existing cluster, but there is no document for how to use an existing cluster to provision new k8s cluster, does there are any document that I can refer? Thanks.

[pierre-emmanuelJ]

This is the same way, just use kubeconfig of your existing cluster. And you can use it with clusterctl or kubectl.
Little example:
https://github.com/exoscale/cluster-api-provider-exoscale/blob/create-cluster-doc/doc/create-cluster-kubectl.md
I use kind in this case but you can use another cluster.
IMPORTANT:
follow the instructions of openstack when you build the provider-configuration to apply it to your existing cluster.

[detiber]

/kind documentation
/priority important-soon
/milestone v1alpha1

[detiber]

/help
/good-first-issue

[k8s-ci-robot]

@detiber:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

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.

[detiber]

I've created a similar set of instructions for using the AWS provider with an existing k8s cluster: https://gist.github.com/detiber/8f61767b6d39d65aceab89d5a92589c4

[ncdc]

/milestone Next

as per discussion at today's Cluster API meeting

[jichenjc]

@gyliu513 maybe we should think about create an openstack own before the cluster API next version.

[ashish-amarnath]

/assign @amy
/lifecycle active

[k8s-ci-robot]

@ashish-amarnath: GitHub didn't allow me to assign the following users: amy.

Note that only kubernetes-sigs 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 @amy
/lifecycle active

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.

[gyliu513]

@amy any progress for this?