Core infrastructure
Under Core Infrastructure → Compute Engine, Cloud Admin focuses on the node that runs your API server: rolling 24h trends for CPU, memory, root filesystem pressure, and network throughput, paired with container runtime versions, kubelet builds, kube-proxy posture, and intent-driven actions that persist as ConfigMaps for reconcilers.
Screens from the live product, with a short note on when you would open each view.
In Node Fleet, the Overview view answers one operational question at a time, node fleet analytics with ready and gpu node counts. Part of compute engine; use it when you need evidence before changing limits, scaling, or opening a ticket.
Click the screenshot to open full size, zoom, and pan.
In Node Fleet, the Issues view answers one operational question at a time, node fleet issues including notready and gpu availability. Part of compute engine; use it when you need evidence before changing limits, scaling, or opening a ticket.
Click the screenshot to open full size, zoom, and pan.
Compute Engine control-plane metrics and kubelet status.
Click the screenshot to open full size, zoom, and pan.
Compute Engine bridges live telemetry with reconciler-ready Intent ConfigMaps. Operators edit purposefully, automation applies consistently, and dashboards stay trustworthy.
Executives read KPI badges while engineers validate kubelet semver against change records.
Explicit kube-proxy deployment notes stop witch hunts when Service routing shifts to eBPF.
Sync Rules couples kubectl rollouts to intent updates, bridges see causality, not mystery reboots.