Confirming the deployment#
Note
After running the helm install command, please wait 5 to 10 minutes for the deployment to stabilize.
To understand whether installation is complete, start by making sure all pods are ready in the kcm-system namespace. There should be 30 pod entries:
kubectl get pods -n kcm-system
NAME READY STATUS RESTARTS AGE
azureserviceoperator-controller-manager-7bd6488fd6-9xnpl 1/1 Running 0 15h
azureserviceoperator-controller-manager-7bd6488fd6-h6lc5 1/1 Running 0 15h
capa-controller-manager-55cfc67958-28rs2 1/1 Running 0 15h
capd-controller-manager-86d454c464-w748z 1/1 Running 0 15h
capg-controller-manager-85bfd498ff-dq6p4 1/1 Running 0 15h
capi-controller-manager-7cdbbff465-jdrkd 1/1 Running 0 15h
capi-ipam-in-cluster-controller-manager-65ff99c687-sjqdc 1/1 Running 0 15h
capi-ipam-infoblox-controller-manager-7799fc8777-pr2sh 1/1 Running 0 15h
capk-controller-manager-6856484b65-75w8k 1/1 Running 0 15h
capo-controller-manager-fbb5f757d-dbscc 1/1 Running 0 15h
capv-controller-manager-6b66c94857-lht5t 1/1 Running 0 15h
capz-controller-manager-6b64b4b4c7-znp7p 1/1 Running 0 15h
helm-controller-78597454d5-dshcp 1/1 Running 0 15h
k0smotron-controller-manager-bootstrap-fbd7cf566-dd2d2 1/1 Running 0 15h
k0smotron-controller-manager-control-plane-7d96d9cbf4-n5wjv 1/1 Running 0 15h
k0smotron-controller-manager-infrastructure-6b5dd9d5f8-78dwg 1/1 Running 0 15h
kcm-cert-manager-6c9c79b447-vsx79 1/1 Running 0 15h
kcm-cert-manager-cainjector-6cd65f4c87-ktvqj 1/1 Running 0 15h
kcm-cert-manager-webhook-5bbb68c7bb-qdll8 1/1 Running 0 15h
kcm-cluster-api-operator-bc9ff7d94-fjbls 1/1 Running 0 15h
kcm-datasource-controller-manager-78b567885b-h9wfg 1/1 Running 0 15h
kcm-k0rdent-enterprise-controller-manager-85c7b99587-nsznq 1/1 Running 0 15h
kcm-k0rdent-ui-94bd98f59-wcxh6 1/1 Running 0 15h
kcm-license-controller-manager-6fbcd66c45-sgzld 1/1 Running 0 15h
kcm-rbac-manager-8568b659-xmnkg 1/1 Running 0 15h
kcm-regional-telemetry-5f759c9654-6bss4 1/1 Running 0 15h
kcm-reloader-547ccdb5df-mr7kq 1/1 Running 0 15h
orc-controller-manager-75679d94fc-md4d6 1/1 Running 0 15h
source-controller-7c8977d7dd-st27c 1/1 Running 0 15h
velero-5cb456f878-gsp4m 1/1 Running 0 15h
kubectl get pods -n kcm-system --no-headers | wc -l
30
State management is handled by Project Sveltos, so you'll want to make sure that all 10 pods are running/completed in the projectsveltos namespace:
kubectl get pods -n projectsveltos
NAME READY STATUS RESTARTS AGE
access-manager-567845d5d4-bxmsn 1/1 Running 0 15m
addon-controller-697b97855f-n24ck 1/1 Running 0 15m
classifier-manager-5d44568fcb-7zg8m 1/1 Running 0 15m
event-manager-d5fd59b7c-qjrbq 1/1 Running 0 15m
hc-manager-67d7794d6d-jhhn6 1/1 Running 0 15m
mcp-server-6d74dc569-xtsck 1/1 Running 0 15m
sc-manager-66db5ff599-plwxb 1/1 Running 0 15m
shard-controller-9c7f46557-qppr7 1/1 Running 0 15m
sveltos-agent-manager-84c847447b-vkptv 1/1 Running 0 14m
techsupport-controller-6798744c4b-wppj9 1/1 Running 0 15m
kubectl get pods -n projectsveltos --no-headers | wc -l
10
If any of these pods are missing, simply give Mirantis k0rdent Enterprise more time. If there's a problem, you'll see pods crashing and restarting, and you can see what's happening by describing the pod, as in:
kubectl describe pod classifieclassifier-manager-5b47b66fc9-5mtwl -n projectsveltos
As long as you're not seeing pod restarts, you just need to wait a few minutes.
Verify that Mirantis k0rdent Enterprise itself is ready#
The actual measure of whether Mirantis k0rdent Enterprise is ready is the state of the Management object. To check, issue this command:
kubectl get Management -n kcm-system
NAME READY RELEASE AGE
kcm True kcm-1-3-0 9m
Verify the templates#
Next verify whether the KCM templates have been successfully installed and reconciled. Start with the ProviderTemplate objects:
kubectl get providertemplate -n kcm-system
NAME VALID
cluster-api-1-1-4 true
cluster-api-provider-aws-1-0-14 true
cluster-api-provider-azure-1-0-18 true
cluster-api-provider-docker-1-0-11 true
cluster-api-provider-gcp-1-0-12 true
cluster-api-provider-infoblox-1-0-6 true
cluster-api-provider-ipam-1-0-7 true
cluster-api-provider-k0sproject-k0smotron-1-0-19 true
cluster-api-provider-kubevirt-1-0-2 true
cluster-api-provider-openstack-1-0-18 true
cluster-api-provider-vsphere-1-0-12 true
k0rdent-enterprise-1-3-0 true
kcm-regional-1-3-0 true
projectsveltos-1-1-1 true
Make sure that all templates are not just installed, but valid. Again, this may take a few minutes.
You'll also want to make sure the ClusterTemplate objects are installed and valid:
kubectl get clustertemplate -n kcm-system
NAME VALID
adopted-cluster-1-0-1 true
aws-eks-1-0-6 true
aws-hosted-cp-1-0-29 true
aws-standalone-cp-1-0-26 true
azure-aks-1-0-5 true
azure-hosted-cp-1-0-31 true
azure-standalone-cp-1-0-21 true
docker-hosted-cp-1-0-6 true
gcp-gke-1-0-10 true
gcp-hosted-cp-1-0-28 true
gcp-standalone-cp-1-0-24 true
kubevirt-hosted-cp-1-0-6 true
kubevirt-standalone-cp-1-0-6 true
openstack-hosted-cp-1-0-24 true
openstack-standalone-cp-1-0-28 true
remote-cluster-1-0-24 true
vsphere-hosted-cp-1-0-27 true
vsphere-standalone-cp-1-0-24 true