Clarify that OOM cgroup messages may not appear in `kubectl describe … #53484
Conversation
…nodes` The current documentation suggests that the OOM cgroup message appears in the output of `kubectl describe nodes`. In practice, this is not always the case may be dependent on the kubelet logging setup. This change clarifies that: - The detailed OOM cgroup log line is not reliably surfaced in `kubectl describe nodes` - Pod level information (`OOMKilled`, exitCode 137) is the reliable place to find OOM events - Kernel/kubelet logs on the node contain the actual cgroup message Motivation: During testing on (Minikube and a GCP managed cluster) environments, the OOM event was consistently visible at the Pod level but the cgroup message was not present in `kubectl describe nodes`, despite appearing in kubelet/journal logs. This clarification helps align user expectations with observed kubelet behavior in different runtime environments. This PR only updates documentation and does not affect code.
|
|
|
Welcome @Srinath04! |
k8s-ci-robot
added
the
cncf-cla: no
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
size/S
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 participants
…nodes`
Description
The current documentation suggests that the OOM cgroup message appears in the output of
kubectl describe nodes. In practice, this is not always the case may be dependent on the kubelet logging setup.This change clarifies that:
kubectl describe nodesOOMKilled, exitCode 137) is the reliable place to find OOM eventsMotivation:
During testing on (Minikube and a GCP managed cluster) environments, the OOM event was consistently visible at the Pod level but the cgroup message was not present in
kubectl describe nodes, despite appearing in kubelet/journal logs. This clarification helps align user expectations with observed kubelet behavior in different runtime environments.This PR only updates documentation and does not affect code.
Issue
N/A