Troubleshoot Issue With Pods

 
Troubleshoot Issue With Pods - Part 1 

To troubleshoot and resolve the issue with the failing pod, you can follow these steps:

1. First, SSH into the host to access the Kubernetes cluster using the configured 

`kubectl` utility.

2. Check the status and logs of the failing pod to identify the specific errors or issues causing the pod not to come up:

   

   # kubectl get pods

   # kubectl describe pod webserver

   # kubectl logs webserver -c httpd-container

   # kubectl logs webserver -c sidecar-container

   

3. Based on the logs and descriptions, identify the root cause of the problem. Common issues could include image pull failures, misconfigured resources, or conflicting ports.

4. If the issue is related to image pull, ensure names `httpd:latest` and `ubuntu:latest' are accessible. If not, consider using specific image tags that are available.

5. Check if there are any resource constraints causing the pod to fail, such as CPU or memory limits.

kubectl describe pod <pod-name> -n <namespace>

Replace <pod-name> with the name of your pod and <namespace> with the appropriate namespace where the pod is located.

In the output of the kubectl describe command, you will find information about the pod's resource limits and requests under the "Limits" and "Requests" sections. Look for the cpu and memory fields to determine if there are any limitations set for CPU and memory.