A court-records Pod terminates with OOMKilled and the remaining log snippet is short. What should the administrator still do when reviewing the failure?
Select an answer to reveal the explanation.
Short Explanation
When the container gets the memory axe, the diary may be a stub—but the last scribbles plus the OOMKilled stamp still tell the story. Pair sparse logs with the termination reason.
Full Explanation
OOMKilled containers often leave truncated or sparse stdout. Administrators should still read whatever last lines remain and correlate them with the reported termination reason and resource limits. Ignoring the reason, blaming DNS, or changing Service TTL does not address memory exhaustion.