Lens doesn't include master node resources in Overview

Lens Support & Troubleshooting
#1

I’m facing an issue with resource summary visualization (CPU and memory) on the Lens Overview page. My cluster has three nodes (each with 4 CPUs and ~8GB RAM), one of which is the master/control-plane. All nodes appear as Ready and have no taints, and the master is available for scheduling pods.

However, the allocatable capacity summary shown in the Lens Overview only displays 8 CPUs and 15.1 GiB of RAM, which corresponds to only two nodes.

When I use kubectl, I correctly see the 12 CPUs and ~22.7 GiB of RAM available:

I have already checked:

  • All nodes, including the master, are visible in Lens and are Ready.
  • There are no taints, ResourceQuotas, or LimitRanges.
  • The metrics-server is working correctly.
  • The master is not protected against pod scheduling.

Question: Is there a specific configuration in Lens to ensure the resource summary in the Overview includes all nodes, including the master/control-plane? Or is this the expected behavior of Lens? How can I ensure that Lens shows the real, total capacity of the cluster in the Overview?

Thanks in advance for your attention and any guidance!

#2

Hello @fernandowilliam84, thanks a lot for the detailed report

What you’re seeing is expected with the current design of Lens. The Overview page shows capacity per node role (Master or Worker), not the total across all nodes. That’s why you only see the Worker node capacity summed up, even though your control-plane node is Ready and schedulable.

There’s no extra configuration needed on your side — Lens isn’t ignoring your master node, it’s just that we don’t currently provide an “all nodes / total cluster capacity” view in the Overview.

We understand this can be confusing, especially when the control-plane is schedulable. We’ve already discussed that it would be useful to add an option or view that shows the true cluster-wide totals (Master + Worker). I’ll make sure your feedback is noted in our backlog.

Thanks again for bringing this up!