Difference between revisions of "Eviction"
Jump to navigation
Jump to search
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | * [[Node-pressure Eviction]] | + | * [[Node-pressure Eviction]]: <code>[[EvictionThresholdMet]]</code> |
− | * [[Killing]] | + | * <code>[[Killing]]</code> |
− | * [[Evict]] | + | * <code>[[Evict]]</code> |
* [[Eviction API]] | * [[Eviction API]] | ||
* [[Kubernetes Pod Disruptions]] | * [[Kubernetes Pod Disruptions]] | ||
Line 12: | Line 12: | ||
* <code>[[karpenter.sh/do-not-evict: true]]</code> | * <code>[[karpenter.sh/do-not-evict: true]]</code> | ||
* <code>[[ttlSecondsUntilExpired]]</code> | * <code>[[ttlSecondsUntilExpired]]</code> | ||
− | * [[Reason:]] | + | * <code>[[Reason:]]</code> |
− | + | * <code>[[controller.node]] [[Triggering termination for expired node after]] 168h0m0s .../...</code> | |
+ | * <code>[[kubectl patch provisioner]]</code> | ||
== Activities == | == Activities == |
Latest revision as of 08:51, 7 September 2023
- Node-pressure Eviction:
EvictionThresholdMet
Killing
Evict
- Eviction API
- Kubernetes Pod Disruptions
- PriorityClass
- qoSClass
Related[edit]
karpenter.sh/do-not-evict: true
ttlSecondsUntilExpired
Reason:
controller.node Triggering termination for expired node after 168h0m0s .../...
kubectl patch provisioner
Activities[edit]
See also[edit]
- Eviction, Eviction API,
kind: Eviction, kubectl cordon
- 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: