{"id":20608,"date":"2020-09-10T23:21:42","date_gmt":"2020-09-10T23:21:42","guid":{"rendered":"https:\/\/rbsitsoftwaresolution.com\/blog\/mirantis-releases-its-first-take-on-the-lens-kubernetes-ide.html"},"modified":"2020-09-10T23:21:42","modified_gmt":"2020-09-10T23:21:42","slug":"mirantis-releases-its-first-take-on-the-lens-kubernetes-ide","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/mirantis-releases-its-first-take-on-the-lens-kubernetes-ide.html","title":{"rendered":"Mirantis releases its first take on the Lens Kubernetes IDE"},"content":{"rendered":"

The next version of Lens<\/a>, the open-source Kubernetes<\/a> IDE, will be out shortly. This release, Lens 3.6, will be the first since OpenStack cloud<\/a> and Kubernetes power Mirantis took over Lens lead<\/a>.\u00a0<\/p>\n

\n\t\tmust read<\/span>
\n\t<\/h3>\n


\n <\/span><\/p>\n

<\/a><\/p>\n

\n
\n What is Kubernetes? How orchestration redefines the data center
\n <\/a>\n <\/p>\n

In a little over four years’ time, the project born from Google’s internal container management efforts has upended the best-laid plans of VMware, Microsoft, Oracle, and every other would-be king of the data center.<\/p>\n

\n Read More<\/a>\n <\/p>\n

Lens is arguably the most popular of all the Kubernetes IDEs. Although it’s not even a year old yet, Lens already has a community of over 35,000 users and 7,000 GitHub stargazers<\/a>.<\/p>\n

Lens is available on Github<\/a> under the MIT License<\/a>. Some of the largest companies in the world are already using Lens. These include Adobe, Apple, and Zendesk.<\/p>\n

In this first release since Mirantis<\/a> took charge, Lens’ biggest new feature is how it manages Kubernetes cluster access. It now uses kubeconfig<\/a> files directly as cluster references. So, you’ll no longer waste time copy-pasting the contents of those files. Simply choose the files from your filesystem and you’re good to go.<\/p>\n

Previously, this information had been stored internally. It worked fine so long as there was no need to update the kubeconfig file contents. However, many Lens users are using third-party tools from managed Kubernetes service providers to generate their kubeconfig files. These tools also often update them on the fly. Since Lens didn’t update the revised files, this often led to programmer confusion and ticked off developers.\u00a0<\/p>\n

Lens’ built-in Smart Terminal has also gotten smarter. It comes with kubectl<\/a> and other Kubernetes cluster tools. The Smart Terminal will now automatically switch the version of kubectl to match the currently selected cluster Application Programming Interface (API) version. It also automatically switches the context to match your cluster.<\/p>\n

You can also now define which directory you’ll use with Smart Terminal. Before that, if you were working in a restricted environment, you might not have been able to use the Terminal at all because you didn’t have access to the Terminal’s directory.<\/p>\n

\n<\/section>\n

Alternatively, you can disable the Smart Terminal feature and define a path for your preferred kubectl binary. Then, you’ll use that version of kubectl no matter what the Kubernetes cluster you’re working on uses as its default.<\/p>\n

Big changes? No, not really. Important changes? Oh yes. Lens users will want to shift over to this new version as soon as it becomes available. The release candidate is already out. I expect the shipping edition to be out within a week or two.<\/p>\n

Related Stories:<\/strong><\/p>\n