Cluster
The boolean
ready (API and dashboard) is true only when the cluster is running and no pool is mid-operation — poll that instead of parsing statuses.
Node pools
pending → provisioning → running, with scaling / deleting while a background operation runs (the pool’s status message reports the outcome, e.g. a drain blocked by a PodDisruptionBudget).
Nodes
Nodes in
not_ready and cordoned still bill — the VM is running; these states describe Kubernetes scheduling, not the machine.