We are happy to announce a new Stable release for Lens Desktop that addresses multiple bugs and offers a new set of features as a response to the valuable feedback we have gathered from our community.
To ensure a smooth transition and minimize disruption we’ll start by rolling out the update to a small portion of our users, then incrementally increasing this number until all users have access to the update. If you have not received the update and wish to try it out, you can download this version manually at our website .
Here’s what you can expect:
Deployment status now displays in a human-readable format, simplifying the understanding of resource states.
Added new columns to the DaemonSet list, providing comprehensive status details consistent with the information available in kubectl.
Added detailed TLS certificate information for Kubernetes Secrets that hold such data.
Reintroduced icons to the Navigator, making it easier to identify resources within the tree view.
New entries in the command palette to quickly reveal the Teamwork and EKS sections in the navigator.
New entries in the command palette to search & switch to any Kubernetes resource associated with the active cluster.
Prioritized recently selected commands on the command palette.
Prioritized recently selected clusters in the cluster search.
Introduced the ability to bypass the internal proxy for commands such as: Pod/Node shells, Port forwarding, and Helm/Kubectl commands, helping users leveraging services like Tailscale or HAProxy.
Added option to resize pod columns in the Node Details panel.
Fixed styling issues across dropdowns, overlays, the Status Bar, the Command Palette, and more.
Introduced the ability to jump to a parent resource directly from pod logs, and improved JSON formatting in logs for easier debugging.
Restored the ability to remove cluster contexts directly from the navigator.
Introduced display of the active cluster in the status bar to easily identify active resources.
Improved visibility into connection issues by exposing errors when attempting to connect to clusters with malformed kubeconfigs.
Exposed user errors in the AWS CLI config when triggering SSO (EKS integration).
Users can now view logs for authentication errors encountered while connecting to clusters.
Required user confirmation when executing cordon/uncordon of nodes.
Resolved issues with EKS Single Sign-On (SSO) workflows triggered from Lens, accommodating recent AWS API changes.
Addressed bored agent security vulnerabilities.
Fixed welcome/release notes tab not accounting for the tab history.
Fixed bug not allowing to interact with namespace dropdown when user is constrained to just one namespace.
Fixed pod sharing link to properly open the details of the shared pod.
Fixed unhandled error when saving resources in the editor with proper permissions.
Fixed non-clickable “all namespaces” option in namespace filter.
Fixed tab closure on middle click.
Fixed spinner’s position in the pod list within Node details.
Screen Recording
Note: Recently used commands and clusters for easy switching, new “Switch to” entry in the palette to find & open other cluster resources, new DaemonSet columns, Remove Cluster from Kubeconfig action, Icons in the navigator, resizable pods table on Nodes, quick jump to parent resource in logs, and more
Error: Failed to fetch https://downloads.k8slens.dev/apt/debian/dists/stable/main/binary-amd64/Packages.bz2 File has unexpected size (632 != 629). Mirror sync in progress? [IP: 138.199.36.9 443]
Hashes of expected file:
- Filesize:629 [weak]
- SHA512:c850abba6ea1c299cda01233bd166e2991bb1a51d6618530c802da7e28705d7b77847ca43a85e6264e35442d33d4df8d03c15b735994ec71a7cc26c8997fc2d7
- SHA256:808835e2a3488a2c4625f7fee803ebe3f2eb49961d4175dcef606df51569945d
- SHA1:6e04f0fb9fe363e80ffda2fb6eb33c6c9ae37462 [weak]
- MD5Sum:df1d84687ae2eb3d348fcb2cd15fe9f2 [weak]
Release file created at: Fri, 17 Jan 2025 16:24:33 +0000
Error: Some index files failed to download. They have been ignored, or old ones used instead.
Also, in-app Upgrade does not work on Linux for me. I can click the upgrade button and restart, but without any effect.
I’d be happy to see the APT repo fixed and meanwhile have an alternative Link to a .deb file posted here. Thx.
I cannot download this release because of what seems to be a mismatch between what the Release file expects and what’s actually being served by BunnyCDN:
Failed to fetch https://downloads.k8slens.dev/apt/debian/dists/stable/main/binary-amd64/Packages.bz2
File has unexpected size (632 != 629)
Please, if you would just post the links to the binaries, I would be able to sort this out myself. Or, better still, why not just make https://downloads.k8slens.dev/ide/ accessible, and then people can find the version and binary they want themselves?
I was just forcefully upgrade from the last really “working” version 2024.8, so I tried it for some minutes, before going back.
My feedback:
Still mixed Tabs from different clusters, not option to AT LEAST group them per cluster. This is still a major problem
Still no option to have favorite clusters
Still no option to sort clusters in the left area.
The left navigation gets messy, when working with two or more clusters, because the list get’s long very fast, you have to search very long for what you need.
Good:
You brought back Icons
Option to color the clusters.
It’s really sad seeing this bad UI for this very great tool.
Thanks again for the feedback. We are currently working on bringing the hot bar back (to allow bookmarking clusters), an option to quickly filter tabs based on the active cluster to address the mixed tabs using drill down mode, and better navigation to jump between clusters. We’ll for sure let you know once all these are addressed. Some of these will be available in the next release.
I feel exactly the same way for the left navigation.
In the previous version
The quick link “pinned” cluster buttons means you could always quickly switch to other clusters, now you need to scroll a lot. Comparing values/resources between clusters is very cumbersome now.
The other nice thing that is now lost is the view was retained when you navigated between clusters.
When you had a cluster’s catergories all expanded (Workloads,Config,Network) you could click back and forth between clusters and the view position was stored and restored.
now, there’s a very combersome scroll required.
I will certainly revert the version until that (hopefully soon) is restored.
