Lens 5.2 is now available, with many new and improved capabilities and numerous fascinating enhancements and bug fixes! Support for Apple’s Silicon chip (M1), enhanced user experience for adding/removing clusters, Monaco Editor Integration and more.
Let’s dive into all of them, but at first, what’s Lens?
Lens: The Kubernetes IDE
Lens, currently used by more than 250k Kubernetes users, is a useful and free desktop application that will assist you in seeing and controlling your Kubernetes cluster (s). I am well aware of how difficult it may be to manage a k8s cluster. It’s easy to become lost in the command line, but GUIs such as Lens and Portainer can make things easier. It has a high amount of customisation and features you can learn about on the official site.
Better M1 Compatibility
Due to the increased number of workstations powered by Apple M1 Silicon, the Lens team upgraded Electron (which powers the entire Lens desktop program) to version 12, which includes native support for creating binaries targeting M1 machines. This is essential in ensuring that all Lens users have a fantastic experience with improved performance and low bugs.
Want an M1 Silicon to try Lens out? Apply to p3r!
Manipulating Clusters are now easier
After Lens 5 was released, it was apparent that adding and removing a cluster was not providing an outstanding experience. The lens team worked on this to enhance the user experience and here are the new updates:
- They added a new dialog that will guide the user when removing entries from their kubeconfig to boost clarity and assure expected effects when removing clusters.
- Now you can add clusters straight from the Catalog with a single click.
- For better understanding of the feature, UI assistance and indications regarding the use of kubesync for importing and managing clusters from kubeconfigs have been included.
Monaco Editor is your Friend
With this addition, Lens resembles VSCode a little more. The Monaco editor, which is used to power VScode, has a number of features that will also allow Lens to improve its terminal and YAML editing capabilities in the future.
Auto-Join Cluster Tokens
The Auto-Join Cluster Tokens feature was created to help Kubernetes administrators to programmatically onboard their clusters to Lens Spaces. This capability is appropriate for users who want to manually link their clusters to Lens Spaces or use a bastion host or leap boxes to access their clusters.
Create an auto-join cluster token in your Lens Space and use it to install the required components into your cluster. After a few seconds, your cluster should appear in your Lens Space!
Other Notable Updates
- Added ability to rename Hotbars
- Improved namespace selection UX
- Copying of Kubernetes resource names from UI is easier
- Added metrics to namespaces and jobs
Notable bug removals:
- Updated packaged kubectl to v1.21.2 to improve port-forward connections
- Improved dashboard updates to reflect cluster changes in nodes and CRD views
- Catalog sidebar font size variations fixed
- Fixed metrics loading for various Kubernetes resources
- Hotbars are limited to 12 slots
I hope this post helped you to get in sync with what’s happening with Lens. Read more of our posts here: