Deployment has Non-Ready Pods

This guide will help you to identify the issues related to non-ready pods.

CRITICAL Alert: Deployment cloud-connect has non-ready pods for longer than a 15m.
CRITICAL Alert: StatefuleSet chi-test-test-0-0 has non-ready pods for longer than a 15m.

How to Identify the Issue?

If you receive an alert indicating that there are non-ready pods, follow these steps to identify the problem:

Locate the Deployment Name:
The alert will contain the deployment name, which will help you identify the pod name. Refer to this section to know how to get the pod name.
Describe the Pod:
Use the following command to describe the pod and find the issue under the Events section:

kubectl describe pod <podname> -n <namespace>

Once you identified the issue, you can further debug and find a solution.

To retrieve the pod name, follow these steps:

Download Kubernetes Credentials:
Navigate to the Environment Overview tab and click K8s Credentials to download the Kubernetes credentials.
Export the Kubernetes Configuration:
Use the following command to export the kubeconfig:

export KUBECONFIG=~/path/to/<kubeconfig>

Retrieve the Pod Name:
Run the following command to get the list of pods and identify the pod associated with the deployment name:

kubectl get pods -n <namespace> | grep -i <deployment-name/statefulset-name>

After retrieving the pod name, refer to this section to describe the pod and identify the issue.