ReadinessProbe | BestHub

Efficient Ops

Nov 14, 2023 · Cloud Native

Why Did My Kubernetes Pods Stop Communicating? Uncovering CoreDNS ReadinessProbe Failures

A sudden Kubernetes outage was traced to a CoreDNS ReadinessProbe failure on port 8181, and the article walks through symptom detection, code‑level root‑cause analysis, and a ConfigMap fix that restores inter‑pod communication.

CoreDNSReadinessProbecloud-native

0 likes · 8 min read

Why Did My Kubernetes Pods Stop Communicating? Uncovering CoreDNS ReadinessProbe Failures

Ops Development Stories

Jun 1, 2021 · Cloud Native

Why Do Readiness Probe Failures Show “OCI runtime exec failed: EOF” in Kubernetes?

A Kubernetes pod reported readiness probe warnings with an OCI runtime exec failure, which was traced through kubelet, Docker, dockershim, containerd, and runc, ultimately caused by a race condition with cpu‑manager updating the container state file, and resolved by disabling cpu‑manager or upgrading runc.

OCI runtimeReadinessProbecontainerd

0 likes · 14 min read

Why Do Readiness Probe Failures Show “OCI runtime exec failed: EOF” in Kubernetes?