General troubleshooting methods for VMware Telco Cloud Automation.
Getting kubeconfig of the VMware Telco Cloud Automation cluster
curl -XGET --user "bootstrapperVMUsername:bootstrapperVMPassword" "https://{bootstrapperVMIP}:9443/api/admin/clusters?clusterType=MANAGEMENT"
curl -XGET --user "bootstrapperVMUsername:bootstrapperVMPassword" "https://{bootstrapperVMIP}:9443/api/admin/clusters/{clusterName}/kubeconfig?clusterType=MANAGEMENT"
API returns JSON response, use kubeconfig to get the base64 encoded kubeconfig. Perform a bas64 decode of the kubeconfig and use decoded value for the kubectl, helm commands.
Obtain Deployment List
- For VMware Telco Cloud Automation manager, use the command
kubectl get deployments -n tca-mgr. - For VMware Telco Cloud Automation Control Plane, use the command
kubectl get deployments -n tca-system.
$ kubectl get deployments -n tca-mgr NAME READY UP-TO-DATE AVAILABLE AGE istio-ingressgateway 1/1 1 1 32h redisoperator 1/1 1 1 32h rfs-redisfailover 3/3 3 3 32h tca-api 2/2 2 2 31h tca-app 1/1 1 1 31h tca-catalog-parser 1/1 1 1 31h tca-helm-service 1/1 1 1 31h tca-k8s-event-collector 1/1 1 1 31h tca-platform-manager 1/1 1 1 31h tca-prometheus-proxy 1/1 1 1 31h tca-resource-change-monitor 1/1 1 1 31h tca-ui 1/1 1 1 31h
$ kubectl get deployments -n tca-system NAME READY UP-TO-DATE AVAILABLE AGE hostconfig-operator 1/1 1 1 31h istio-ingressgateway 1/1 1 1 31h k8s-bootstrapper 1/1 1 1 31h nfv-ccli 1/1 1 1 31h nodeconfig-operator 1/1 1 1 32h redisoperator 1/1 1 1 31h rfs-redisfailover 3/3 3 3 31h tca-api 2/2 2 2 31h tca-app 1/1 1 1 31h tca-helm-service 1/1 1 1 31h tca-k8s-event-collector 1/1 1 1 31h tca-platform-manager 1/1 1 1 31h tca-prometheus-proxy 1/1 1 1 31h tca-resource-change-monitor 1/1 1 1 31h tca-ui 1/1 1 1 31h vmconfig-operator 1/1 1 1 32h
Check Statefulset
-
To obtain the statefulset for VMware Telco Cloud Automation manager, use the command
kubectl get statefulset -n tca-mgr. - To obtain the statefulset for VMware Telco Cloud Automation Control Plane, use the command
kubectl get statefulset -n tca-system.
$ kubectl get statefulset -n tca-mgr NAME READY AGE kafka 3/3 32h mongodb 3/3 32h rfr-redisfailover 3/3 32h tca-tcf-manager 1/1 32h zookeeper 3/3 32h
$ kubectl get statefulset -n tca-system NAME READY AGE kafka 3/3 31h mongodb 3/3 31h rfr-redisfailover 3/3 31h zookeeper 3/3 31h
Restart deployment
To restart the deployed service, use the command kubectl rollout restart deployment/<name-of-deployment> -n tca-system.
Status of restart
To check the status of the restart of service, use the command kubectl rollout status deployment/<name-of-deployment> -n tca-system.
Replace <name-of-statefulset> with the actual name of the deployment service.
Example
$ kubectl rollout status deployment/tca-api -n tca-syatem Waiting for deployment "tca-api" rollout to finish: 1 out of 2 new replicas have been updated... Waiting for deployment "tca-api" rollout to finish: 1 out of 2 new replicas have been updated... Waiting for deployment "tca-api" rollout to finish: 1 out of 2 new replicas have been updated... Waiting for deployment "tca-api" rollout to finish: 1 old replicas are pending termination... Waiting for deployment "tca-api" rollout to finish: 1 old replicas are pending termination... deployment "tca-api" successfully rolled out
Obtaining Stateful service name
To obtain the stateful status, use the command get statefulset -n tca-system.
Example
$ kubectl get statefulset -n tca-system NAME READY AGE kafka 3/3 31h mongodb 3/3 31h rfr-redisfailover 3/3 31h zookeeper 3/3 31h
Restart statefulset
kubectl rollout restart statefulset/<name-of-statefulset> -n tca-system
Replace <name-of-statefulset> with the actual name of the statefulset service. You can obtain the name of the stateful server using the command get statefulset kubectl.
Status of Restart statefulset
kubectl rollout status statefulset/<name-of-statefulset> -n tca-system
Replace <name-of-statefulset> with the actual name of the statefulset service. You can obtain the name of the stateful server using the command get statefulset kubectl.
