How To Give Developers Secure Access to Kubernetes Clusters using Lens

Setting up a Kubernetes service has become relatively easy, whether it be on-premise or in public cloud services. However, giving secure access to developers can be a painful process involving cluster certificates, access management systems, networking setup, and firewalls. Administrators typically do not want to expose their Kubernetes clusters on a public network directly. Instead, to secure access to developers, they either stay on a private network or create VPN access for remote work, and it is not only expensive but challenging to set up. When you work with multiple clusters in different clouds, it requires numerous VPNs, and giving developers access becomes a true challenge.

To address this challenge, Lens Cloud is introduced. You’ll have an option to share access to your cluster and accept invitations from others to access their clusters. To make this possible Team Lens introduced a new technology called Cluster Connect. This allows Developers and Operators to easily access and work with their clusters anywhere, without having to go through a complex onboarding process to obtain a KUBECONFIG file.

In this Tech-Talk, We will demonstrate how you can securely share access to your Kubernetes cluster without dealing with configuration files.