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!
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 .
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:
Unfortunately, this is one of the most challenging UI/UX experiences Iāve encountered:
1-The removal of the Hotbar makes navigation less efficient, and now I can barely read my cluster names without straining.
2-The removal of extensions significantly hampers productivity
I finally threw Lens Desktop away and went back to OpenLens, which works like a charm. The product was completely broken, I constantly encounter empty sheets, I have to restart the entire application every half hour. Navigation has become absolutely inconvenient. And a lot of other problems. Itās a shame to see something good become bad. I apologize for the negative message, Iām just very annoyed. I hope for a bright future for this wonderful project.
Personally, I reverted to the last version with the old UI (Lens.2024.11.62028-latest.exe).
But I agree, itās frustratingāthis product was great before, and then boom, with one update, it became completely unusable.
Lens did a magic thing where it installed itself into the c:\program files dir when it suppose to be in the APPDATA dir.
Open it up normally, got version 2024.11.1261604 with an upgrade flag.
Upgraded to 2025.2.141554 successfully then quit the app to see if fixed issue (below).
Checked version again and it ārevertedā to 2024.11.1261604. This looped happened religiously for a few minutes.
Checked and both APPDATA and C:\ProgramFiles had a Lens instance installed. Hard - deleted both folders as both were executing and triggering the update process.
downloaded the lasest exe āLens Setup 2025.2.141554-latestā from Lensā website, installed and the upgrade loop stopped.
Now back to the main problem.
Using AKS, azcli, kubelogin and Az RBAC admin roles on Windows, Lens does not show the content of any namespace on any page. Connected to docker-desktop k8s and EKS with built in roles and not an issue.
My MacBook does not have any of these issues.
Apparently, its been an off and on issue since pre 2022 and the workaround is to copy kubelogin.exe to the ~Lens\resources\cli\bin directory. This worked in December but no longer works and now Lens is a nice 1.something gb of unusable space.
openLens works without a workaround.
k9s works without a workaround.
azcli (obviously) works without a workaround.