Core readiness signals
| Signal | How to read it |
|---|---|
| Desired vs ready | A growing gap often matters more than an isolated warning event. |
| Strategy | Helps explain whether the workload is expected to change gradually or all at once. |
| Exposure | Shows whether the workload participates in a service or ingress path. |
| Last activity | Gives context for whether the workload was recently touched or is quietly stable. |
When to look beyond the workload
- Open pod details if the workload is degraded but only one pod looks unhealthy.
- Open node details if multiple pods on one host show similar symptoms.
- Open namespace details if several workloads in the same boundary are affected.
ExampleA workload can remain mostly ready while one replica churns. In that case, treat the workload as partially healthy and inspect the affected pod before escalating.