Managing Kubernetes clusters entirely from the command line is a rite of passage. We have all typed kubectl get pods -n kube-system more times than we care to admit. But when you are troubleshooting a cascading failure across multiple namespaces at 3:00 AM, staring at raw JSON or
Freelens: Taking back control of your Kubernetes clusters with a truly open-source desktop client
Managing Kubernetes clusters entirely from the command line is a rite of passage. We have all typed kubectl get pods -n kube-system more times than we care to admit. But when you are troubleshooting a cascading failure across multiple namespaces at 3:00 AM, staring at raw JSON or squinting at nested YAML in a terminal window isn't just exhausting—it is a liability.
Enter Freelens, a free, open-source, cross-platform desktop application designed to take the squinting out of Kubernetes administration.
If Freelens looks familiar, that is because it is a direct fork of OpenLens, the open-source core that originally powered Mirantis's popular Lens Desktop. When the commercial version of Lens began locking features behind paywalls and subscription models, the community did what the community does best: they forked it.
Freelens is built to preserve the dream of a powerful, unrestricted, and highly extensible Kubernetes IDE. It runs locally on your machine, respects your existing kubeconfig files, and does not require you to sign up for a cloud account just to view your local development clusters.
Freelens is built using Electron, meaning it runs natively across macOS, Linux, and Windows. Below is the breakdown of how to get it running on your machine of choice.
Freelens requires macOS 12 (Monterey) or later. The project provides native binaries for both Apple Silicon (arm64 for M1/M2/M3 chips) and Intel (amd64) architectures.
If you use Homebrew, you can install the cask with a single command:
brew install --cask freelens
Alternatively, you can download the .dmg or .pkg installers directly from the Freelens Releases page.
To run Freelens on Linux, your system must have GNU C Library (glibc) 2.34 or later. This is standard on modern distributions such as Debian 12, Fedora 35, Ubuntu 22.04, Arch Linux, and their derivatives.
The Flatpak package is hosted on Flathub. It comes bundled with kubectl and helm, and automatically reads your local ~/.kube/config.
To install and run it:
flatpak install flathub app.freelens.Freelens
flatpak run app.freelens.Freelens
Note on Flatpak Sandboxing: Because Flatpak runs applications in an isolated environment, Freelens includes built-in wrappers to access host-installed CLI tools like aws, doctl, gke-gcloud-auth-plugin, and kubelogin. If you need to drop into a terminal within Freelens, it defaults to /bin/sh inside the sandbox, but you can configure it to use /app/bin/host-spawn to interact directly with your host system's shell.
For Ubuntu and other Snap-enabled distributions:
sudo snap install freelens --classic
If you prefer native package management via apt, you can add the official repository:
# Add the repository signing key
curl -L https://raw.githubusercontent.com/freelensapp/freelens/refs/heads/main/freelens/build/apt/freelens.asc | sudo tee /etc/apt/keyrings/freelens.asc
# Add the source list
curl -L https://raw.githubusercontent.com/freelensapp/freelens/refs/heads/main/freelens/build/apt/freelens.sources | sudo tee /etc/apt/sources.list.d/freelens.sources
# Update and install
sudo apt update
sudo apt install freelens
Arch users can find the precompiled binary package in the AUR under freelens-bin.
If you prefer a portable executable, grab the .AppImage from the releases page. First, ensure you have the necessary fuse and compression libraries installed:
sudo apt install libfuse2 zlib1g-dev
Then, run the AppImage with the recommended flags to ensure smooth rendering under modern display servers (like Wayland) and to bypass sandbox-related GPU issues:
./Freelens*.AppImage --no-sandbox --ozone-platform-hint=auto --enable-features=WebRTCPipeWireCapturer --enable-features=WaylandWindowDecorations --disable-gpu-compositing
Freelens supports Windows 10 or later, offering native builds for both x64 and arm64 architectures.
You can install Freelens silently using Microsoft's native package manager:
winget install Freelensapp.Freelens
Tip: Use the --scope machine flag if you want to install it globally to C:\Program Files instead of the local user directory.
If you prefer the developer-focused Scoop installer:
scoop bucket add extras
scoop install freelens
If you prefer a zero-installation footprint, download the Portable EXE from the releases page. Standard .exe (NSIS) and .msi installers are also available.
One of the greatest strengths of the original OpenLens ecosystem was its extension API. Freelens maintains full compatibility with this ecosystem. Developers can easily port existing OpenLens extensions or write brand-new ones.
Freelens is a community-driven project that welcomes contributors of all skill levels. Whether you want to fix a bug in the UI, optimize the build pipeline, or write documentation, your help is welcome.
The Freelens project utilizes BountyHub, allowing community members to fund specific feature requests or bug fixes. Developers can claim these bounties by submitting successful pull requests that resolve the issues.
To learn more about how to fund an issue or get paid for your code, check out the Fund an issue or earn money by developing wiki page.
The rapid growth of Freelens is driven by a dedicated group of open-source maintainers:
Stay connected with the community, report bugs, or discuss new feature ideas through these channels:
If your organization uses Freelens, consider adding your name to the official Adopters List to show your support for sustainable open-source software.
Freelens is distributed under the permissive MIT License.
Ya sea que necesites gestionar un millón de H100s o solo quieras asegurarte de que tu agente de IA no tire un rm -rf / en producción, las actualizaciones del Next '26 de GKE sugieren que el futuro de la IA es, inevitablemente, un archivo YAML.
copy fail in kubernetes: when your pod escapes to the host with four bytes if you thought containers were a
