Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Cluster API Provider for VMware Cloud Director
[ad_1]
#here bootstrap.conf is kubeconfig of the bootstrap cluster from 1st section.
kubectl —kubeconfig=bootstrap.conf apply –f capi–mgmt.yaml
#check the cluster status
root@jump:~# kubectl get clusters
NAME PHASE
mgmt–cluster Provisioned
root@jump:~#
#After successful deployment of the mgmt-cluster, check the machine status
root@jump:~# kubectl get machines
NAME PROVIDERID PHASE VERSION
mgmt–cluster–control–plane–24n5m vmware–cloud–director://urn:vcloud:vm:a62758c0-dfc3-4d6b-a436-f0b6d283567f Running v1.21.2+vmware.1
mgmt–cluster–control–plane–7x4w2 vmware–cloud–director://urn:vcloud:vm:76ae58f7-3141-4598-8ac2-8cc703a950cf Running v1.21.2+vmware.1
mgmt–cluster–control–plane–x8rql vmware–cloud–director://urn:vcloud:vm:a677be71-d2e1-483f-8307-4450ea60fddb Running v1.21.2+vmware.1
mgmt–cluster–md0–c579f7887–d8hv4 vmware–cloud–director://urn:vcloud:vm:98338cfd-aaf0-4432-9a2f-8550a6a46e24 Running v1.21.2+vmware.1
#Fetch the kubeconfig of the mgmt-cluster
clusterctl get kubeconfig mgmt–cluster > mgmt–cluster.kubeconfig
#use mgmt-cluster config to work with the new management cluster
export KUBECONFIG=mgmt–cluster.kubeconfig
#root@jump:~# kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
cert–manager cert–manager–848f547974–fmxs5 1/1 Running 0 26h
cert–manager cert–manager–cainjector–54f4cc6b5–9qlzz 1/1 Running 0 26h
cert–manager cert–manager–webhook–7c9588c76–g94nx 1/1 Running 0 26h
kube–system antrea–agent–hm6vd 2/2 Running 0 35h
kube–system antrea–agent–pjqbl 2/2 Running 0 35h
kube–system antrea–agent–sjjhn 2/2 Running 0 35h
kube–system antrea–agent–z4qdg 2/2 Running 0 35h
kube–system antrea–controller–64bcc67f94–8lv7c 1/1 Running 0 35h
kube–system coredns–8dcb5c56b–snx29 1/1 Running 0 35h
kube–system coredns–8dcb5c56b–tznlp 1/1 Running 0 35h
kube–system csi–vcd–controllerplugin–0 3/3 Running 0 35h
kube–system csi–vcd–nodeplugin–kjw5w 2/2 Running 0 35h
kube–system etcd–capi–cluster–control–plane–24n5m 1/1 Running 0 35h
kube–system etcd–capi–cluster–control–plane–7x4w2 1/1 Running 0 35h
kube–system etcd–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–24n5m 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–7x4w2 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–controller–manager–capi–cluster–control–plane–24n5m 1/1 Running 1 35h
kube–system kube–controller–manager–capi–cluster–control–plane–7x4w2 1/1 Running 1 35h
kube–system kube–controller–manager–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–proxy–jnjl2 1/1 Running 0 35h
kube–system kube–proxy–lw6m7 1/1 Running 0 35h
kube–system kube–proxy–m7gls 1/1 Running 0 35h
kube–system kube–proxy–nsv9m 1/1 Running 0 35h
kube–system kube–scheduler–capi–cluster–control–plane–24n5m 1/1 Running 1 35h
kube–system kube–scheduler–capi–cluster–control–plane–7x4w2 1/1 Running 1 35h
kube–system kube–scheduler–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system vmware–cloud–director–ccm–75bd684688–pcktg 1/1 Running 1 35h
#convert this cluster to work as management cluster by installing Cluster API
clusterctl init —core cluster–api:v0.4.2 –b kubeadm:v0.4.2 –c kubeadm:v0.4.2
kubectl apply –k cluster–api–provider–cloud–director/config/default
root@jump:~# kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
capi–kubeadm–bootstrap–system capi–kubeadm–bootstrap–controller–manager–7dc44947–zdhvd 1/1 Running 1 26h
capi–kubeadm–control–plane–system capi–kubeadm–control–plane–controller–manager–cb9d954f5–7snk2 1/1 Running 0 26h
capi–system capi–controller–manager–7594c7bc57–mvpvx 1/1 Running 0 26h
capvcd–system capvcd–controller–manager–6bd95c99d8–8fzvf 1/1 Running 0 26h
cert–manager cert–manager–848f547974–fmxs5 1/1 Running 0 26h
cert–manager cert–manager–cainjector–54f4cc6b5–9qlzz 1/1 Running 0 26h
cert–manager cert–manager–webhook–7c9588c76–g94nx 1/1 Running 0 26h
kube–system antrea–agent–hm6vd 2/2 Running 0 35h
kube–system antrea–agent–pjqbl 2/2 Running 0 35h
kube–system antrea–agent–sjjhn 2/2 Running 0 35h
kube–system antrea–agent–z4qdg 2/2 Running 0 35h
kube–system antrea–controller–64bcc67f94–8lv7c 1/1 Running 0 35h
kube–system coredns–8dcb5c56b–snx29 1/1 Running 0 35h
kube–system coredns–8dcb5c56b–tznlp 1/1 Running 0 35h
kube–system csi–vcd–controllerplugin–0 3/3 Running 0 35h
kube–system csi–vcd–nodeplugin–kjw5w 2/2 Running 0 35h
kube–system etcd–capi–cluster–control–plane–24n5m 1/1 Running 0 35h
kube–system etcd–capi–cluster–control–plane–7x4w2 1/1 Running 0 35h
kube–system etcd–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–24n5m 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–7x4w2 1/1 Running 0 35h
kube–system kube–apiserver–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–controller–manager–capi–cluster–control–plane–24n5m 1/1 Running 1 35h
kube–system kube–controller–manager–capi–cluster–control–plane–7x4w2 1/1 Running 1 35h
kube–system kube–controller–manager–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system kube–proxy–jnjl2 1/1 Running 0 35h
kube–system kube–proxy–lw6m7 1/1 Running 0 35h
kube–system kube–proxy–m7gls 1/1 Running 0 35h
kube–system kube–proxy–nsv9m 1/1 Running 0 35h
kube–system kube–scheduler–capi–cluster–control–plane–24n5m 1/1 Running 1 35h
kube–system kube–scheduler–capi–cluster–control–plane–7x4w2 1/1 Running 1 35h
kube–system kube–scheduler–capi–cluster–control–plane–x8rql 1/1 Running 0 35h
kube–system vmware–cloud–director–ccm–75bd684688–pcktg 1/1 Running 1 35h
[ad_2]