Difference between revisions of "Killing: Stopping container"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | |||
| + | |||
| + | [[Kubelet]]: | ||
<code>[[Killing: Stopping container]] XXXXX</code> | <code>[[Killing: Stopping container]] XXXXX</code> | ||
| Line 8: | Line 9: | ||
</pre> | </pre> | ||
| + | |||
| + | <code>[[Evict]]</code> | ||
== Related == | == Related == | ||
Revision as of 15:16, 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
Advertising:
