Difference between revisions of "Node-pressure eviction"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 8: | Line 8: | ||
* <code>[[imagefs]]</code> | * <code>[[imagefs]]</code> | ||
* <code>[[BestEffort]], [[Burstable]], [[Guaranteed]]</code> | * <code>[[BestEffort]], [[Burstable]], [[Guaranteed]]</code> | ||
| − | |||
* [[OOMKiller]] | * [[OOMKiller]] | ||
* [[FreeDiskSpaceFailed]] | * [[FreeDiskSpaceFailed]] | ||
Revision as of 15:11, 9 March 2023
Node-pressure eviction is the process by which the kubelet proactively terminates pods to reclaim resources on nodes.
Related
- Kubelet logs
imagefsBestEffort, Burstable, Guaranteed- OOMKiller
- FreeDiskSpaceFailed
- QosClass
- Eviction
- PodPhase
- API-initiated Eviction
- Kubernetes Pod Disruptions
- NodeReady
See also
- Killing
- Kubernetes nodes,
node.kubernetes.ioK8s Node controller (node-controller),MemoryPressure, DiskPressure, NodeHasDiskPressure, events, NodeNotReady, Node-pressure Eviction, RemovingNode, ProviderID,kubectl node-shell, kubectl describe nodes 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- 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:
