Freelens

Freelens is a free, open-source desktop interface for exploring and managing Kubernetes clusters. It is designed for developers, platform engineers and cluster administrators who want visual access to workloads, configuration, networking, storage, events and access-control resources alongside terminal-based tools.

Cluster visibility and management

Connect existing Kubernetes contexts through kubeconfig to browse nodes, namespaces, pods, deployments and other resources. Workload views, pod logs, shell and attach actions, port forwarding, resource editing and Helm management support investigation and day-to-day administration. Metrics depend on the cluster's available metrics-server or Prometheus-compatible data and your access to them; installing the desktop client does not automatically install a monitoring stack in every cluster.

Freelens is a community fork of OpenLens, the open-source core of Lens Desktop. It carries that code forward as a separate application. It is not a paid Lens subscription, a Mirantis account entitlement or a guarantee that every commercial Lens feature or third-party extension is included. Optional extensions have their own compatibility, permissions and service requirements.

Credentials, tools and permissions

You need an existing reachable Kubernetes API endpoint and valid cluster credentials. The client uses kubeconfig contexts, commonly from ~/.kube/config; selected contexts determine which cluster and identity an operation targets. Protect kubeconfig files, embedded tokens, certificates and authentication plugins as credentials. Cloud-provider authentication can require separately installed provider tools and a provider account; a bundled kubectl does not replace every external credential helper.

Version 1.10.3 bundles kubectl 1.36.2 and Helm 4.2.2. Their paths and related preferences can be configured, and external binary failures are reported by the application. Binary selection and Kubernetes version compatibility should be checked for the cluster you administer. A separate Homebrew kubectl or Helm installation is not a prerequisite solely because these tools exist in the interface. The terminal can invoke local programs with your user permissions, while pod shell, attach, Helm changes, resource editing and deletion can perform remote actions using your Kubernetes authorization.

Kubernetes RBAC and server admission policies still control permitted actions. Freelens does not grant cluster-admin permissions or bypass a cluster's authentication. Use the intended context and namespace before changing resources: a desktop GUI action can affect a production cluster. Grant only the local file/network access and remote privileges required for your work. Running the Mac application does not ordinarily require making every cluster credential an administrator credential.

Installation and platforms

Install the freelens Homebrew Cask or use the official DMG or PKG for your Mac architecture. macOS 12 or later is required by both the official README and Cask dependency. Apple Silicon uses the arm64 build, while Intel uses the amd64 build. The recorded 1.10.3 arm64 DMG is 199,473,494 bytes by official HTTP HEAD; this is installer size rather than installed disk use. The stable Cask conflicts with freelens@nightly, so choose one channel rather than treating both as interchangeable installations.

The project also distributes Windows and Linux packages separately. The desktop application is installed on your workstation, not as a Kubernetes server component. It does not create a cloud account, supply a managed cluster or include hosted compute capacity. Internet access may be needed for updates, tool downloads, authentication or remote clusters; private clusters may require your organization's network route or VPN.

License, fees and optional services

Freelens is free under the MIT license, with notices for Freelens and OpenLens authors. No paid Freelens desktop license or Lens account is required for the base client. Donations and community funding are optional. Kubernetes hosting, cloud providers, commercial support and optional extensions or model APIs may have separate charges and terms; they are not included merely by installing the app.

The client handles local credentials and connects to the clusters and services you configure. Logs, terminal output, resource manifests and screenshots can reveal infrastructure details or secrets, so share only appropriate material. The official screenshot is a historical illustrative Mac workload/log view rather than proof of the exact 1.10.3 interface or a hosted cluster included with the product.

Official sources: Tagged README, MIT license, Releases, Project wiki.