hello @dechegaray , i love the revamped navigator, but unless I´m missing something, i think you guys removed the option to ctrl + f cluster names, right?
Also, i realized that its easy to end up with multiple clusters’ opened at the same time. could you also add a button to collapse all?
@mario.martinez hi, thank you for your feedback. I’ve added the collapse button to our backlog, and we’re considering the search feature for Navigator also.
The new cluster navigation is awful. The repetition of all sub items that can be individually expanded makes for a terrible navigation experience. I only manage 3 clusters and I hate this already.
Also the new UI is extremely slow at loading anything with more resources… It takes almost 10 seconds to load 600 pods for all namespace.
I uninstalled after one day and went back to the old 2023 version.
3 Likes
Hello there, thanks for providing your feedback.
We are aware of the performance issues when loading new Kube resources, and the team is working hard to provide a patch that will improve this behavior considerably. Our aim is to cut the loading times so when subsequent resources for the same cluster are open, the operation feels instant (as it was in the previous version of Lens).
We are also introducing new UX improvements soon, that will allow users to jump between clusters easier and have better control of the new navigation sidebar.
1 Like
@dechegaray Thanks for the update on performance issues. It’s been a struggle to perform daily work tasks with the latest beta. I’m looking forward to the next version. The excellent features of the newer betas make it worth my time to wait a little bit for the screens to load. Thank you!
I’m glad that I had the previous version download in place, so I could easily rollback. Navigation and UI of new version could definitely be better, the old version looks cleaner and simpler (It is actually so much better and I can really see it only after the new shiny version experience).
The bugs with state updates/refresh and general feeling of slowness and lagginess is really annoying (and awful).
1 Like
We appreciate the feedback @jlamoree . Stay tuned for future updates where will be addressing these issues 
I am missing the new version in the Linux (.deb) repo … ;-(
1 Like
Hi @jeansen , we are working on fixing the missing binaries, they will be available in the next couple of days with a couple more fixes. Meanwhile you can download it temporarily from https://api.k8slens.dev/binaries/Lens-2024.9.300059-latest.amd64.deb
Since the new release my app is still crashing. The message: AssertionError [ERR_ASSERTION]: There must be some tab data for a kube resource tabId. Anyone any idea?
Noticing an issue where previously when you click on the namespace, then hit enter it would switch to that namespace. New functionality just adds the current namespace to the enabled namespace. Was this intended?
Hi there, this might be due to a corrupted file. Could you please delete the following folder and restart Lens:
- On MacOS:
/Users/USERNAME/Library/Application Support/Lens/lens-local-storage-v2/main-view-feature - On Windows:
/Users/USERNAME/AppData/Roaming/Lens/lens-local-storage-v2or/Users/USERNAME/AppData/Local/Lens/lens-local-storage-v2(depending on your setup)
We just released a new version of Lens patching a couple of issues, my recommendation would be to do the aforementioned workaround, and install the latest version right after
Hi there. It is intended indeed as we changed the look and feel of the dropdown.
Currently, clicking a namespace adds to the selection, unless you have “All namespaces” selected, in which case, the next click, cleans up everything and selects just the intended target. We are looking of ways to improve this and offer an option to just “switch” between namespaces, so both UX are supported
Noticed a difference between the old way and the new one. When you click on a pod, to see the logs, you used to be able to switch between the common replicas to look at the logs, now you have to go open each one. Was this part of the new UX design as well?
Hello there, sorry for the delay replying. You can still achieve the same behavior by starting the logs from the Workload owner of the pod (Deployment/StatefulSet/Daemonset, etc), instead from the pod directly. We did this change as we were failing to compute accordingly new pods and ReplicaSets appearing after restarts, workloads scaling up/down, etc etc.
Having said that, we are in the process of adding an option to quickly jump from the pod logs to the deployment logs, so you can access the aggregated logs easier. Stay tuned!
I cannot see any updates in the repos, yet. Is this true or am I missing something?
1 Like
Do you mean the Linux repos? if so, you can access our latest beta version with important fixes directly here → Early Access for Linux users (we haven’t published them yet). If not, let me know to what repos you are referring to, so we can help you out
No, I mean the GA releases. The current, official release is available only for Windows and MacOS. For Linux, the latest version in the official APT repo is 2024.8.291605-latest .
1 Like
Understood. We are planning to update the official APT repo once we stabilize a few things more in the product, and do a full roll out of a stable release (next few weeks). Meanwhile you can download the binaries directly from:
Latest stable (2024.10.171859-latest)
Debian-based: Lens-2024.10.171859-latest.amd64.deb
Portable: Lens-2024.10.171859-latest.x86_64.AppImage
RPM-based: Lens-2024.10.171859-latest.x86_64.rpm
Beta (2024.11.51849-beta)
We highly encourage to use this one as there are a lot of performance improvements included here:
Debian-based: Lens-2024.11.51849-beta.amd64.deb
Portable: Lens-2024.11.51849-beta.x86_64.AppImage
RPM-based: Lens-2024.11.51849-beta.x86_64.rpm