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 20 pod entries:
kubectl get pods -n kcm-system
NAME READY STATUS RESTARTS AGE
azureserviceoperator-controller-manager-7c9f777c69-sjrnw 1/1 Running 0 13m
capa-controller-manager-6dbbf886cc-7xscr 1/1 Running 0 12m
capd-controller-manager-5c6859dc88-k4mjq 1/1 Running 0 12m
capg-controller-manager-7c9659c479-g7pgq 1/1 Running 0 12m
capi-controller-manager-747d6ff9dc-gstpx 1/1 Running 0 14m
capi-ipam-in-cluster-controller-manager-67b74d8954-ggszp 1/1 Running 0 14m
capi-ipam-infoblox-controller-manager-8bb9dd788-nhqmf 1/1 Running 0 14m
capo-controller-manager-5f84bf558f-ltsqc 1/1 Running 0 12m
capv-controller-manager-5f95f66c84-fwbbm 1/1 Running 0 12m
capz-controller-manager-8698f8b7d5-ndbhg 1/1 Running 0 13m
helm-controller-5fcc8b9746-qb9wg 1/1 Running 0 17m
k0smotron-controller-manager-bootstrap-79ffc45fb-klckd 1/1 Running 0 14m
k0smotron-controller-manager-control-plane-794f4f4f69-pbxfg 1/1 Running 0 14m
k0smotron-controller-manager-infrastructure-67bc6cb47b-fpc6b 1/1 Running 0 12m
kcm-cert-manager-cainjector-6c9675896-f475f 1/1 Running 0 17m
kcm-cert-manager-d57c9d746-9ghpr 1/1 Running 0 17m
kcm-cert-manager-webhook-74876fbbc9-gflfv 1/1 Running 0 17m
kcm-cluster-api-operator-5b9464dd8b-4tqlm 1/1 Running 0 15m
kcm-datasource-controller-manager-7989f5c9fc-hqxpl 1/1 Running 0 17m
kcm-k0rdent-enterprise-controller-manager-8565c7f5cb-9jt22 1/1 Running 0 15m
kcm-k0rdent-ui-74fc54dc87-c68ql 1/1 Running 2 (11m ago) 17m
kcm-rbac-manager-84fc4f7bb8-6qbt9 1/1 Running 0 17m
kcm-regional-telemetry-8b5999c76-hzhxx 1/1 Running 0 17m
source-controller-6c9bcd67f8-rc6cg 1/1 Running 0 17m
velero-74f79f7868-h4rbm 1/1 Running 0 17m
kubectl get pods -n kcm-system --no-headers | wc -l
25
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-2-1 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-0-7 true
cluster-api-provider-aws-1-0-9 true
cluster-api-provider-azure-1-0-9 true
cluster-api-provider-docker-1-0-5 true
cluster-api-provider-gcp-1-0-6 true
cluster-api-provider-infoblox-1-0-2 true
cluster-api-provider-ipam-1-0-3 true
cluster-api-provider-k0sproject-k0smotron-1-0-11 true
cluster-api-provider-openstack-1-0-10 true
cluster-api-provider-vsphere-1-0-6 true
k0rdent-enterprise-1-2-1 true
kcm-regional-1-2-1 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-4 true
aws-hosted-cp-1-0-21 true
aws-standalone-cp-1-0-20 true
azure-aks-1-0-1 true
azure-hosted-cp-1-0-22 true
azure-standalone-cp-1-0-19 true
docker-hosted-cp-1-0-4 true
gcp-gke-1-0-6 true
gcp-hosted-cp-1-0-19 true
gcp-standalone-cp-1-0-17 true
openstack-hosted-cp-1-0-12 true
openstack-standalone-cp-1-0-21 true
remote-cluster-1-0-18 true
vsphere-hosted-cp-1-0-18 true
vsphere-standalone-cp-1-0-17 true