A municipal reporting Pod restarts repeatedly. The last log lines cut off mid-request, and kubectl describe pod shows the previous container terminated with reason OOMKilled. What is the best conclusion?
Select an answer to reveal the explanation.
Short Explanation
When logs stop cold and describe says OOMKilled, the process got the memory axe—like a water main shutting off mid-shower. Bump the limit or slim the app’s footprint. Do not chase DNS or selectors for an OOM reason.
Full Explanation
OOMKilled means the container’s memory usage crossed its cgroup limit and the kernel/kubelet terminated it. Correlating abrupt log cutoff with the describe termination reason confirms memory pressure rather than an image-pull, Service-selector, or DNS failure. Remediation is adjusting resources.limits.memory, reducing application memory consumption, or both, then rolling out the change.