Open the cluster → Metrics tab in my.cubepath.com.
NoteThis tab is coming soon. CPU, memory and network metrics for your cluster nodes will appear here.
How to get metrics today
Kubernetes ships with no metrics pipeline, so nothing collects usage until you install something. Two options from the Addons tab:
| Add-on | What it gives you |
|---|---|
| Metrics Server | The basics: kubectl top nodes, kubectl top pods, and the data the Horizontal Pod Autoscaler needs to scale on CPU or memory. No history, no dashboards |
| Prometheus Stack | Full monitoring: metric collection with history, alerting rules, and Grafana dashboards |
ImportantInstall Metrics Server even if you don't want dashboards. Without it
kubectl topreturns an error and the Horizontal Pod Autoscaler can't scale at all — it's a dependency, not a nicety.
Node-level metrics in the meantime
Each worker is a VPS, so its own Metrics tab already charts CPU, memory, disk and network for that machine — and you can put a Cloud Alert on any of it.
That's the right layer for "is this node saturated?". It won't tell you which pod is responsible, which is exactly what Metrics Server or Prometheus adds.