Kubernetes
586 incident problems in Kubernetes environments.
Read first
When the ConfigMap changed but the Pod keeps using the old valuesAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when values don't refresh after a ConfigMap update because of envFrom, subPath, volume projection, or rollout trigger differences.Kubernetes3 min readWhen CoreDNS is Running but only DNS lookups failAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when the CoreDNS Pod looks healthy but failures occur in the kube-dns path, upstream, node-local-dns, or policy.Kubernetes3 min readWhat to check first when CrashLoopBackOff appearsAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when a Pod restarts repeatedly and the real cause is left in the previous logs and events.Kubernetes3 min read
Recommended problems
Reviewed problems first, then problems with detailed scenarios.
K8S-1611A pod is Running and one Service still has no endpointsA Service shows zero endpoints right after an app label rename.ReviewedKubernetesBeginner6 minFreeK8S-1612A CoreDNS pod is healthy and one namespace still resolves old namesOne namespace still resolves old names after a DNS suffix update.ReviewedKubernetesBeginner6 minFreeK8S-1621A ServiceMonitor is correct and one target still reads zeroOne ServiceMonitor still shows zero targets after a namespace label update.ReviewedKubernetesBeginner6 minFreeK8S-1631A Service is correct and one app still has no endpointsA Service still shows no endpoints after a label cleanup.ReviewedKubernetesBeginner6 minFree
All problems (586)
K8S-1612A CoreDNS pod is healthy and one namespace still resolves old namesOne namespace still resolves old names after a DNS suffix update.ReviewedKubernetesBeginner6 minFreeK8S-1611A pod is Running and one Service still has no endpointsA Service shows zero endpoints right after an app label rename.ReviewedKubernetesBeginner6 minFreeK8S-1631A Service is correct and one app still has no endpointsA Service still shows no endpoints after a label cleanup.ReviewedKubernetesBeginner6 minFreeK8S-1621A ServiceMonitor is correct and one target still reads zeroOne ServiceMonitor still shows zero targets after a namespace label update.ReviewedKubernetesBeginner6 minFreeK8S-1617A Deployment rollout hangsA rollout hangs after moving the app port behind a sidecar.KubernetesBeginner8 minFreeK8S-1707A HorizontalPodAutoscaler sees metrics and one target still reads zeroAn HPA still reads zero after metric exposure was fixed.KubernetesBeginner8 minFreeK8S-1786A readiness path is corrected and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFreeK8S-1796A readiness path is fixed and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFreeK8S-1806A readiness path is fixed and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFreeK8S-1726A readiness probe is correct and one pod still stays unreadyA pod still stays unready after a readiness probe fix.KubernetesBeginner8 minFreeK8S-1766A readiness probe is corrected and one pod still stays unreadyA pod still stays unready after a probe fix.KubernetesBeginner8 minFreeK8S-1706A readiness probe is fixed and one pod still stays unreadyA pod still stays unready after the probe path was fixed.KubernetesBeginner8 minFreeK8S-1736A readiness probe is fixed and one pod still stays unreadyA pod still stays unready after a probe fix.KubernetesBeginner8 minFreeK8S-1746A readiness probe is fixed and one pod still stays unreadyA pod still stays unready after a probe fix.KubernetesBeginner8 minFreeK8S-1756A readiness probe path is correct and one pod still stays unreadyA pod still stays unready after the probe path was corrected.KubernetesBeginner8 minFreeK8S-1716A readiness probe path is fixed and one pod still stays unreadyA pod still stays unready after a probe fix.KubernetesBeginner8 minFreeK8S-1776A readiness probe path is fixed and one pod still stays unreadyA pod still stays unready after a probe fix.KubernetesBeginner8 minFreeK8S-1816A readiness probe path is fixed and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFreeK8S-1826A readiness probe path is fixed and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFreeK8S-1836A readiness probe path is fixed and one pod still stays unreadyA pod still stays unready after the readiness fix.KubernetesBeginner8 minFree