The latest articles on DEV Community by Veeresh (@veeresh_devops). https://dev.to/veeresh_devops https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3653896%2Fef9de356-f7ac-4d1a-947b-b488361e0f81.png https://dev.to/veeresh_devops en Veeresh Sun, 21 Dec 2025 16:28:12 +0000 https://dev.to/veeresh_devops/k8s-pod-failures-4d86 https://dev.to/veeresh_devops/k8s-pod-failures-4d86 <p>Here are 5 pod failures you'll actually face </p> <ol> <li>ImagePullBackOff - "No basic auth credentials." Your node needs an IAM role with ECR permissions.</li> </ol> <p>Check: kubectl describe node | grep iam<br> No role = No image pulls. Attach AmazonEC2ContainerRegistryReadOnly policy.</p> <ol> <li><p>"Exec format error"<br> You built the image on your Mac M2. EKS nodes run AMD64.<br> Fix: Always build with --platform linux/amd64</p></li> <li><p>"Connection refused" to database<br> Your RDS security group isn't allowing traffic from your NODE security group.</p></li> </ol> <p>Add inbound rule: Allow port 5432 from sg-node-xxxxx</p> <ol> <li>"Environment variable not set" Secret exists but in wrong namespace. Or wrong key name.</li> </ol> <p>Check: kubectl get secret -n </p> <p>Match the key names exactly in your secretKeyRef.</p> <ol> <li>CrashLoopBackOff with no logs App needs more startup time than your liveness probe allows. Increase initialDelaySeconds in your probe from 10s to 30s.</li> </ol> <p>Follow for more!</p> kubernetes devops containers