Node health
Node health tells you whether the machines under your workloads are ready to run pods. Read it from the Nodes page and, for dedicated nodes, from node metrics.
Node status#
Open Infrastructure→Nodes. The Status column has two values:
| Status | Meaning |
|---|---|
| Running | The node is ready and schedulable: it's healthy and accepts new pods. |
| Stopped | The node isn't ready, or it's cordoned so new pods won't be placed on it. Pods already on it may still be running. |
Use Refresh to reload the table.
Dedicated node metrics#
For a dedicated node, Nodes→⋮→View metrics shows the whole machine's CPU, Memory, Net In and Net Out over 5m to 24h. These totals help you plan capacity. A node that stays close to its full CPU or memory has little room for another replica, and adding one would lead to another node being leased.
Shared nodes don't expose machine metrics, because their totals include other tenants. Use deploy and pod metrics instead.
What to do when a node isn't healthy#
- Check your workloads first: Deployment status tells you whether your pods are running.
- If a dedicated node stays Stopped and your pods are Pending, contact support from Organisation→Support and include the node name.