Cluster Capacity Snapshot
Quantitative node-capacity signals and scheduling headroom captured directly from the Kubernetes bundle.
Operator
Infrastructure
Stabilize the payments-api rollout: inspect CrashLoopBackOff logs, fix the bad image reference/pull failure, and address memory pressure so pods can schedule and remain healthy.
Reduce exposure in the payments namespace: confirm the public LoadBalancer is required, then implement default-deny NetworkPolicies and restrict any external access to only approved sources.
Harden the payments-api workload: replace the default service account with a least-privilege dedicated account, disable token automount if not needed, and add resource requests/limits plus readiness/liveness probes.
Quantitative node-capacity signals and scheduling headroom captured directly from the Kubernetes bundle.
Autoscaling, disruption, quota, and namespace-default coverage that changes how operators should interpret capacity signals.
Short, operator-oriented callouts for scheduling, rollout, and failing-workload evidence.
A compact operator view of severity and signal distribution before you drop into detailed findings.
Filter the findings table by signal or severity while keeping the current visible count in view.
Detailed review
Expanded explanation for operators who want the model summary after reviewing the findings table.