Difference between revisions of "Killing: Stopping container"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
[[containerd]] Task XXXXXXXX [[deleted with exit code 137]] | [[containerd]] Task XXXXXXXX [[deleted with exit code 137]] | ||
* [[Node-pressure Eviction]] | * [[Node-pressure Eviction]] | ||
| − | * <code>[[Started: Started container]]</code> | + | * [[Kubelet logs]]: <code>[[Started: Started container]]</code> |
| − | |||
== See also == | == See also == | ||
Revision as of 16:46, 2 January 2023
Kubelet:
Killing: Stopping container XXXXX
kubectl get pod termination-demo -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"
Related
containerd Task XXXXXXXX deleted with exit code 137
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions,/etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI),crictl,context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs,manager: kubelet
Advertising:
