I’m new to Kubernetes / k3s, and so also new to Lens.
I don’t understand the different options to have metrics in Lens.
Even this GitHub issue did not clarify it: Metrics not available on k3s · Issue #6520 · lensapp/lens · GitHub
K3s has by default a “metrics-server” service in the “kube-system” namespace.
Can this service provide metrics to show in Lens?
N.B. I’m trying to avoid installing additional things since my homelab cluster is very thin on resources.
Hi! Metrics-server allows to fetch metrics for the current moment but it does not provide any historical data. That’s why Lens is relying on Prometheus to display metrics for the last 1 hour. If you want to try Prometheus out you can enable built-in Prometheus on cluster settings.
For example, in cluster settings
You can try to enable bundled Prometheus
ok, I understand. Thank you for the response.
Still, to show by default as a fallback at least what the metrics-server can provides could be better than nothing.
As can be seen in the right part of the image below, some “current moment” metrics are shown in Lens.
As an alternative to K3s you may want to look at open source k0s. k0s is an all-inclusive Kubernetes distribution, configured with all of the features needed to build a Kubernetes cluster simply by copying and running an executable file on each target host.
k0s allows extensions so that you can extend the configuration of the cluster to include Prometheus, as per the docs here
Finally, please note that k0s is also embedded within Lens Pro version, and is known as Lens Desktop Kube.
I did not know about K0s. Sounds interesting.
What are the advantages over K3s?
How does it compare regarding memory usage?