Persistent Storage
3 incident problems about Persistent Storage. Start with the reviewed ones.
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.
All problems (3)
K8S-1198Stateful workload appears healthy until rescheduleA workload seems safe in steady state, and community examples suggest using local cache for speed. After eviction or node loss, recovery exposes that one critical path was never durable.KubernetesAdvanced25 minProK8S-1187PVC stays Pending after a chart cleanup removed the explicit storage classA StatefulSet worked before, but a chart refactor removed storageClassName and the cluster default no longer provisions compatible volumes.KubernetesAdvanced26 minProK8S-1213PVC is bound but the pod still misses rollout windowsA stateful workload gets its PVC but still appears hung every time it starts.KubernetesAdvanced20 minPro