Kubernetes Infrastructure : Clusters
A cluster is the highest-level unit of a Kubernetes deployment — a control plane plus a set of worker nodes. The Clusters screen gives you one table across every cluster Kloudfuse monitors, so you can compare capacity and usage across regions and cloud providers without switching context.
Table columns
Each row is one cluster. Columns:
| Column | What it shows |
|---|---|
Cluster |
The cluster’s name. |
Age |
Time since the cluster was first seen by Kloudfuse. |
Versions |
The Kubernetes version(s) running across the cluster’s nodes — more than one value here means a rolling upgrade is in progress or nodes are on mixed versions. |
Nodes |
Number of nodes in the cluster. |
CPU Total / CPU Allocable / CPU Used |
Combined CPU cores across all nodes, the portion available for scheduling workloads, and real-time usage by active pods. |
Memory Total / Memory Allocable / Memory Used |
Combined memory across all nodes, the portion allocable to workloads, and real-time consumption. |
Pods Total / Pods In Use / Pods % Usage |
Total pod capacity across the cluster’s nodes, how many pods are currently running, and the resulting utilization percentage. |
Use COLUMNS to add or remove columns, and Download to export the current table.
Details pane
Click any row to open the cluster’s detail pane. Unlike every other Kubernetes resource kind, a cluster has no single Kubernetes manifest, so its detail pane has four tabs instead of the usual five — no YAML:
- Details
-
Cluster, Age, Versions, Nodes, and the CPU/Memory/Pods totals from the table above.
- Metrics
-
Cluster-wide CPU, memory, network, and disk usage as time-series charts. Use the chart time selector to zoom between recent activity (last 5m, 1h) and longer trends (24h) to correlate a spike with a specific window.
- Logs
-
Application and system logs from anywhere in the cluster, with full-text search, tag selection, and time-range filters. Narrow to a specific namespace or pod with the search bar or the tags-and-labels panel first if you already know where to look.
- Events
-
Cluster-wide Kubernetes events — scheduling decisions, restarts, warnings, and failed operations — each with a timestamp and source controller. Combine with Logs and Metrics for faster root-cause analysis.