Difference between revisions of "Killing: Stopping container"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* <code>[[kubectl get events -A]]</code> | * <code>[[kubectl get events -A]]</code> | ||
* <code>[[Unhealthy]]</code> | * <code>[[Unhealthy]]</code> | ||
| + | * <code>[[livenessProbe]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 09:45, 1 May 2024
Kubelet:
Killing: Stopping container XXXXX
kubectl get pod termination-demo -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"
Errors[edit]
Related[edit]
- Nominate
EvictOOMKilledFailedSchedulingcontainerd Task XXXXXXXX deleted with exit code 137- Node-pressure Eviction
- Kubelet logs:
Started: Started container kubectl get events -AUnhealthylivenessProbe
See also[edit]
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:
