node condition
A named fact the kubelet reports about its node, such as Ready, MemoryPressure or DiskPressure, each true or false with a reason.
In more detail
kubectl describe node lists them with their last heartbeat and transition times. Ready summarises the node's health; the pressure conditions explain resource trouble. The control plane turns some conditions into taints.
Example
kubectl describe node node-aRelated terms
- NotReady — A node status meaning its Ready condition is false or unknown, so the control plane no longer trusts it to run pods.
- node pressure — A node condition reporting that it is running short of memory, disk or process IDs, which leads to taints and evictions.
- status condition — A named true-or-false fact that a controller records in an object's status, such as Ready, Available or Accepted, with a reason and a time.
Taught in
- Worker Nodes: kubelet, Runtime, CNI And kube-proxy — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: OOMKilled, Throttling And Evictions — Kubernetes: Production-Grade Container Orchestration
- etcd Snapshots And A Tested Restore — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: NotReady Nodes And kubelet Logs — Kubernetes: Production-Grade Container Orchestration
- A Tiny CRD, Controller And The Operator Pattern — Kubernetes: Production-Grade Container Orchestration