cluster-api: [question] where to check if target cluster doesn't have cluster-api object

User Story

As a [developer/user/operator] I would like to [high level description] for [reasons]

Detailed Description I am trying to migrate openstack provider from v1alpha2 to v1alpha3 with https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/503

now follow the https://master.cluster-api.sigs.k8s.io/clusterctl/commands/move.html I am able to create a cluster (control plane) but there is no such pods such as capi-controller-manager-xx and no definition for cluster, machinedeployment etc

I guess it’s not pivoting from bootstrap cluster now ? can someone help to provide some guide on if this kind of scenario happens, what should I check? do I need explict run pivoting at v1alpha3 now? thanks

root@jj-master:~/go/src/sigs.k8s.io/cluster-api-provider-openstack/examples/output# kubectl --kubeconfig kubeconfig get nodes
NAME                          STATUS   ROLES    AGE     VERSION
test-cluster-controlplane-0   Ready    master   8m57s   v1.17.1
root@jj-master:~/go/src/sigs.k8s.io/cluster-api-provider-openstack/examples/output# kubectl --kubeconfig kubeconfig get pods
No resources found.
root@jj-master:~/go/src/sigs.k8s.io/cluster-api-provider-openstack/examples/output# kubectl --kubeconfig kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE
kube-system   calico-kube-controllers-564b6667d7-h5zv2              1/1     Running   0          8m45s
kube-system   calico-node-gjnqf                                     1/1     Running   0          8m45s
kube-system   coredns-6955765f44-8t5tk                              1/1     Running   0          8m45s
kube-system   coredns-6955765f44-jxhs6                              1/1     Running   0          8m45s
kube-system   etcd-test-cluster-controlplane-0                      1/1     Running   0          9m1s
kube-system   kube-apiserver-test-cluster-controlplane-0            1/1     Running   0          9m1s
kube-system   kube-controller-manager-test-cluster-controlplane-0   1/1     Running   0          9m1s
kube-system   kube-proxy-6cng6                                      1/1     Running   0          8m45s
kube-system   kube-scheduler-test-cluster-controlplane-0            1/1     Running   0          9m1s

[A clear and concise description of what you want to happen.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 15 (15 by maintainers)

Most upvoted comments

I am able to create cluster now (though some other problems still existing), so I close this issue, thanks a lot for your help~

$KUBECONFIG is still set to use /root/.kube/kind-config-clusterapi even though that file has been deleted, remember to unset it Creating cluster “clusterapi” … ✓ Ensuring node image (kindest/node:v1.15.0) 🖼 ✓ Preparing nodes 📦 ✓ Creating kubeadm config 📜 ✓ Starting control-plane 🕹️ ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 Cluster creation complete. You can now use the cluster with:

export KUBECONFIG=“$(kind get kubeconfig-path --name=“clusterapi”)” kubectl cluster-info performing init…

cluster-api CoreProvider installed (v0.3.0)
kubeadm-bootstrap BootstrapProvider installed (v0.3.0)
kubeadm-control-plane ControlPlaneProvider installed (v0.3.0)
openstack InfrastructureProvider installed (v0.5.0)

Your cluster API management cluster has been initialized successfully!

You can now create your first workload cluster by running the following:

jichenjc on Feb 10, 2020

made some progress based on the info above, @fabriziopandini able to create part of the containers and now facing following error , assume it’s related to provide specific issue so working on that, thanks a lot ！

 bin/clusterctl init --core cluster-api:v0.3.0 --bootstrap kubeadm-bootstrap:v0.3.0 --infrastructure openstack:v0.5.0 --control-plane kubeadm-control-plane:v0.3.0
performing init...
Error: failed to create provider object apiextensions.k8s.io/v1beta1, Kind=CustomResourceDefinition, /openstackclusters.infrastructure.cluster.x-k8s.io: CustomResourceDefinition.apiextensions.k8s.io "openstackclusters.infrastructure.cluster.x-k8s.io" is invalid: [spec.versions: Invalid value: []apiextensions.CustomResourceDefinitionVersion{apiextensions.CustomResourceDefinitionVersion{Name:"v1alpha2", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc00534dff8), Subresources:(*apiextensions.CustomResourceSubresources)(nil), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}, apiextensions.CustomResourceDefinitionVersion{Name:"v1alpha3", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc005cf0000), Subresources:(*apiextensions.CustomResourceSubresources)(nil), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}}: must have exactly one version marked as storage version, status.storedVersions: Invalid value: apiextensions.CustomResourceDefinitionVersion{Name:"v1alpha3", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc005cf0000), Subresources:(*apiextensions.CustomResourceSubresources)(nil), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}: must have the storage version v1alpha3]

jichenjc on Feb 6, 2020