Kubernetes / Cluster Operations, Access & Incident Response
Compare schedulable allocatable resources with physical node capacity
A server's advertised capacity is not all available to ordinary Pods. Reservations and already requested resources affect scheduling.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl describe node node01Read the result
Capacity, allocatable and allocated requests provide different views. Actual utilization is not interchangeable with declared requests.
Resolve and verify
Compare the pending workload's requests with allocatable headroom and system reservations. Right-size measured demand or obtain appropriate capacity through the cluster owner.
Before changing production
Do not shrink reservations or invent tiny requests to bypass scheduling while leaving the node vulnerable to pressure.