Kubernetes monitoring overview
What you get (cluster, node, pod, service, storage and event views) and how the agent works.
What you get
The Kubernetes page (left nav, under Monitor) gives every connected cluster a live, drill-down view of its state. Pick a cluster from the cards (or the Cluster selector) and work through tabs that mirror how you think about a cluster:
| Tab | Shows |
|---|---|
| Cluster Overview | Health score, control-plane components, CPU/memory utilization, node and pod summaries, recent warnings. |
| Nodes | Per-node status, CPU/memory bars, pod counts; click a node for conditions (MemoryPressure, DiskPressure), capacity and labels. |
| Pods & Workloads | Pods with status, restarts, resource use; filter by namespace or status (including CrashLoopBackOff). |
| Services & Networking | Services, types, IPs, ports and endpoint counts. |
| Storage | Persistent volumes, claims and storage classes. |
| Events & Alerts | Cluster events (reason, object, message, count) with a critical-alerts banner. |
Six KPI tiles (nodes, pods, services, CPU, memory, active alerts) sit above the tabs, and the page auto-refreshes every 20 seconds. Every row click opens a detail drawer — no context switch.
How it works
You install one agent per cluster. The VerOps Kubernetes agent is a single small binary deployed twice by one Helm install: a one-replica Deployment that watches the Kubernetes API (nodes, workloads, services, storage, events — full object detail) and a DaemonSet that reads real CPU/memory usage from each node's kubelet. It needs only read-only RBAC and an outbound HTTPS connection — no inbound ports.
Two ways to connect a cluster
The easiest way to connect a cluster is the in-app wizard: open the Kubernetes page and click Connect a cluster. It guides you step-by-step — create or choose an API key, pick the VerOps agent or OpenTelemetry, copy a personalized config — and detects automatically when your cluster's first data arrives.
VerOps accepts Kubernetes data from two sources, and each cluster card shows which one feeds it (a VerOps Agent or OTel source chip):
- VerOps Kubernetes agent (recommended) — full object inventory, native events, live agent heartbeats, one-command install.
- OpenTelemetry collector — ships aggregated k8s metrics into the same platform; the right choice when you already operate an OTel pipeline.
See Install the Kubernetes agent for the full comparison and both setups.
If the page shows Connect your first Kubernetes cluster, no cluster is reporting yet — follow the install article. First data appears about a minute after the agent starts.