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-r42ns 1/1 Running 0 116m
capa-controller-manager-7c9f4489bf-swd4l 1/1 Running 0 116m
capd-controller-manager-cfdb7888b-sctvc 1/1 Running 0 116m
capg-controller-manager-6db646964f-qjh4g 1/1 Running 0 116m
capi-controller-manager-8776cc459-dlfsg 1/1 Running 0 117m
capi-ipam-in-cluster-controller-manager-7db7d84768-sj9m2 1/1 Running 0 117m
capi-ipam-infoblox-controller-manager-6c9d8d5dcf-ggbvw 1/1 Running 0 117m
capo-controller-manager-7f6d74fcc6-m98rz 1/1 Running 0 116m
capv-controller-manager-7bc588f67f-dgkr6 1/1 Running 0 116m
capz-controller-manager-58bd78ffd-xk4d7 1/1 Running 0 116m
helm-controller-5fcc8b9746-6mjpj 1/1 Running 0 120m
k0smotron-controller-manager-bootstrap-69df9f4565-br4rz 1/1 Running 0 117m
k0smotron-controller-manager-control-plane-fb8f5cb8f-9jk58 1/1 Running 0 117m
k0smotron-controller-manager-infrastructure-86dd979d67-bmxqf 1/1 Running 0 116m
kcm-cert-manager-6849df6fb-rlb2v 1/1 Running 0 120m
kcm-cert-manager-cainjector-7848877cdf-r8skf 1/1 Running 0 120m
kcm-cert-manager-startupapicheck-tw7fc 0/1 Completed 0 120m
kcm-cert-manager-webhook-64dc9c59f8-qsj2t 1/1 Running 0 120m
kcm-cluster-api-operator-7564c54bd6-pt75m 1/1 Running 0 118m
kcm-k0rdent-enterprise-controller-manager-7687df7564-l78fk 1/1 Running 0 118m
kcm-k0rdent-ui-7685dc4df9-fhhkx 1/1 Running 0 120m
kcm-velero-6658d7f654-lf2f9 1/1 Running 0 120m
source-controller-6b4d78bd56-sk6l2 1/1 Running 0 120m
kubectl get pods -n kcm-system --no-headers | wc -l
23
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-6b57f75bc5-s4v2b 1/1 Running 0 118m
addon-controller-78b85cc98b-b8q9z 1/1 Running 0 118m
classifier-manager-6f987f986d-t7crn 1/1 Running 0 118m
event-manager-7dc76c9899-rdmjq 1/1 Running 0 118m
hc-manager-688b6b4f46-xpfp5 1/1 Running 0 118m
sc-manager-bb555c788-86ls2 1/1 Running 0 118m
shard-controller-546885d8fb-r2dkh 1/1 Running 0 118m
sveltos-agent-manager-d979d4675-vbtml 1/1 Running 0 117m
techsupport-controller-67bbd54745-hcwhd 1/1 Running 0 118m
kubectl get pods -n projectsveltos --no-headers | wc -l
9
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-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-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-12 true
cluster-api-provider-openstack-1-0-10 true
cluster-api-provider-vsphere-1-0-6 true
k0rdent-enterprise-1-2-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-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-22 true
gcp-gke-1-0-4 true
gcp-hosted-cp-1-0-21 true
gcp-standalone-cp-1-0-20 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