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 21 pod entries:
kubectl get pods -n kcm-system
NAME READY STATUS RESTARTS AGE
azureserviceoperator-controller-manager-557c4bc8dc-shg4x 1/1 Running 0 2m22s
azureserviceoperator-controller-manager-557c4bc8dc-tfqm6 1/1 Running 0 2m22s
capa-controller-manager-6f4db96656-tzjrp 1/1 Running 0 2m2s
capd-controller-manager-5977fc677-jql8m 1/1 Running 0 117s
capg-controller-manager-668955d6f9-h94ff 1/1 Running 0 110s
capi-controller-manager-66ccd9d8dd-w8bg7 1/1 Running 0 3m12s
capi-ipam-in-cluster-controller-manager-56c7bd877c-wjc5l 1/1 Running 0 2m50s
capi-ipam-infoblox-controller-manager-548877ddb5-5xcvs 1/1 Running 0 2m48s
capk-controller-manager-769dc57dc8-r8sqk 1/1 Running 0 104s
capo-controller-manager-7b55784585-fhjpb 1/1 Running 0 108s
capv-controller-manager-64664f5cf4-s244l 1/1 Running 0 119s
capz-controller-manager-d849cfbc6-5zkrt 1/1 Running 0 2m22s
helm-controller-5466948d9f-746fm 1/1 Running 0 5m40s
k0smotron-controller-manager-bootstrap-8658fbfcb8-t98zt 1/1 Running 0 2m53s
k0smotron-controller-manager-control-plane-595fdc8c84-vh67z 1/1 Running 0 2m47s
k0smotron-controller-manager-infrastructure-5bcdbb4f78-5mhc8 1/1 Running 0 2m8s
kcm-cert-manager-69b946fdb9-2h9bd 1/1 Running 0 5m40s
kcm-cert-manager-cainjector-757fd85d77-tj54b 1/1 Running 0 5m40s
kcm-cert-manager-webhook-59f6c49756-5bprs 1/1 Running 0 5m40s
kcm-cluster-api-operator-bdb86f9fc-d2w2c 1/1 Running 0 3m49s
kcm-controller-manager-5b6675b94f-x8cwf 1/1 Running 0 3m49s
kcm-rbac-manager-7579db64d9-tb7gx 1/1 Running 0 5m40s
kcm-regional-telemetry-69f8ddbc9-mr6sc 1/1 Running 0 5m40s
kcm-reloader-fc9cbb8cf-rsb98 1/1 Running 0 5m40s
source-controller-597784bdbb-rwsqf 1/1 Running 0 5m40s
velero-b7b646967-zwbxv 1/1 Running 0 5m40s
kubectl get pods -n kcm-system --no-headers | wc -l
26
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-74b7c98d8b-npj6t 1/1 Running 0 20m
addon-controller-6ddb848fdf-5vpnc 1/1 Running 0 20m
classifier-manager-57d5779966-ft9vs 1/1 Running 0 20m
event-manager-5569df975f-4cgrf 1/1 Running 0 20m
hc-manager-66c559fff6-l6xnx 1/1 Running 0 20m
mcp-server-55459fdccf-sg4lj 1/1 Running 0 20m
sc-manager-56ccc48477-lvz66 1/1 Running 0 20m
shard-controller-6b65cd4f8f-kmpps 1/1 Running 0 20m
sveltos-agent-manager-97d78f4bb-hqjm6 1/1 Running 0 19m
techsupport-controller-797459769b-wwg6h 1/1 Running 0 20m
kubectl get pods -n projectsveltos --no-headers | wc -l
10
If any of these pods are missing, simply give k0rdent 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 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-3 true
cluster-api-provider-aws-1-0-13 true
cluster-api-provider-azure-1-0-16 true
cluster-api-provider-docker-1-0-10 true
cluster-api-provider-gcp-1-0-11 true
cluster-api-provider-infoblox-1-0-5 true
cluster-api-provider-ipam-1-0-6 true
cluster-api-provider-k0sproject-k0smotron-1-0-16 true
cluster-api-provider-openstack-1-0-15 true
cluster-api-provider-vsphere-1-0-11 true
kcm-1-8-0 true
kcm-regional-1-8-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-2 true
aws-eks-1-0-4 true
aws-hosted-cp-1-0-23 true
aws-standalone-cp-1-0-22 true
azure-aks-1-0-3 true
azure-hosted-cp-1-0-25 true
azure-standalone-cp-1-0-22 true
docker-hosted-cp-1-0-25 true
gcp-gke-1-0-4 true
gcp-hosted-cp-1-0-23 true
gcp-standalone-cp-1-0-22 true
openstack-hosted-cp-1-0-24 true
openstack-standalone-cp-1-0-24 true
remote-cluster-1-0-19 true
vsphere-hosted-cp-1-0-19 true
vsphere-standalone-cp-1-0-18 true
Verify k0rdent status#
The final test of whether k0rdent installation is installed is making sure the
status of the Management object itself is True:
kubectl get management -n kcm-system
NAME READY RELEASE AGE
kcm True kcm-1-8-0 18m