You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The cluster is four Raspberry Pi 5 running Debian 64-bit lite.
I let Lens install prometheus and node-exporter, and for the nodes tab I see usage except on the memory row (see screenshot 1). The overall view (screenshot 2) works fine.
To Reproduce
Steps to reproduce the behavior:
Go to the nodes tab
Expected behavior
The memory "bar" being colored.
Screenshots
Screenshot 1a (no memory usage showing):
Screenshot 1b (after clicking on a node):
Screenshot 2 (overall dashboard looking fine):
Environment (please complete the following information):
Lens Version: 2024.1.170738-latest
OS: [e.g. OSX] macOS 14.2.1 (M2)
Installation method (e.g. snap or AppImage in Linux): DMG file
Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
Additional context
I hope the screenshots explain enough of the issue.
I have tried running a stress test to make a pod use around 4GB of memory, but it still didn't show up on the memory bar.
The text was updated successfully, but these errors were encountered:
Describe the bug
The cluster is four Raspberry Pi 5 running Debian 64-bit lite.
I let Lens install prometheus and node-exporter, and for the nodes tab I see usage except on the memory row (see screenshot 1). The overall view (screenshot 2) works fine.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The memory "bar" being colored.
Screenshots
Screenshot 1a (no memory usage showing):
Screenshot 1b (after clicking on a node):
Screenshot 2 (overall dashboard looking fine):
Environment (please complete the following information):
Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
Additional context
I hope the screenshots explain enough of the issue.
I have tried running a stress test to make a pod use around 4GB of memory, but it still didn't show up on the memory bar.
The text was updated successfully, but these errors were encountered: