Debugging Helm Test Issues

To debug Helm Test issues:

• Execute the following command to get the Helm Test pod name.

  kubectl get pods -n <deployment-namespace>

• Check for the Helm Test pod that is in error state.

  Figure 5-12 Helm Test Pod

  
• Execute the following command to check the Helm Test pod:

  kubectl logs <helm_test_pod_name> -n <deployment_namespace>

  In the logs, concentrate on ERROR and WARN level logs. There can be multiple reasons for failure. Some of hem are shown below:

  Figure 5-13 Helm Test in Pending State

  

  In this case, check for CPU and Memory availabality in the kubernetes cluster.

  Figure 5-14 Pod Readiness Failed

  

  In this case, check for readiness proble url correctness in the particular microservice helm charts under charts folder. In the above case, check for charts of notify service [OR] check if the pod is crashing for some reason when the url configured for readiness probe is correct.

• There are few other cases where the httpGet parameter is not configured for Readiness probe. In this case, Helm Test is considered as success for that pod. And if the Pod/PVC list is fetched based on namespace and labelSelector is empty, the helm test is considered as success.