The cluster view
Open a connected cluster and you get twelve tabs. Each one answers a different question, and each carries a count badge so you can see where the work is before you click.
| Tab | The question it answers |
|---|---|
| Risk | Which workloads are riskiest right now, and why? |
| Namespaces | Which namespaces are failing or degraded? |
| Workloads | What is running, is it ready, is it restarting? |
| Services | What is exposed inside the cluster? |
| Ingress | What is exposed outside it? |
| Nodes | Where is capacity, and which nodes are unhealthy? |
| Upgrade Readiness | What breaks on the next Kubernetes hop? |
| Security | Misconfigurations, CVEs and compliance posture. |
| Changes | What changed, when, and what exactly was different? |
| Reliability | Deploy frequency, change-failure rate, MTTR. |
| Right-Sizing | Which requests are wrong, and what should they be? |
| Access | Who can touch this cluster? |
Everything on these tabs is derived from what the read-only agent synced. Nothing here writes to your cluster — see the RBAC & security model.
Two axes, one list
Section titled “Two axes, one list”Risk is scored on two axes — upgrade risk and security risk — and correlated by workload. The cross-axis panel on Upgrade Readiness is where that correlation surfaces: a workload that both blocks the upgrade and carries unresolved CVEs is one piece of work, not two, and it is the one to do first.