Credential access
Reads kubeconfig, cluster tokens, and pod/secret views allowed by the current context.
brew / rank 281
Install k9s with Homebrew
Kubernetes CLI To Manage Your Clusters In Style! Version 0.51.0 via Homebrew; verified 2026-07-27.
agent safety
Agent safety answer
k9s is an interactive Kubernetes UI with cluster read and mutation capability.
Remote mutation
Can delete, edit, scale, and exec into Kubernetes resources.
Publish/artifact risk
Can change live workloads and configuration.
Recommended control
Gate launch in privileged contexts and commands that mutate resources.
Agent-use guidance
Use read-only contexts for agents; require approval before interactive cluster mutation.
install
Additional install commands
macOS
Homebrewverified · 100%
brew install k9sprovider-native install command
overview
Package summary
Kubernetes CLI To Manage Your Clusters In Style!
Project links
Commands and aliases
- k9s
history
Project history and usage
K9s is a terminal user interface for Kubernetes that turns cluster navigation, inspection, and common operations into a keyboard-driven local app. It became one of the recognizable post-kubectl tools for operators who wanted a faster view of resources without moving into a full graphical dashboard.
Project history
The derailed/k9s repository was created in January 2019. The project describes K9s as a Kubernetes CLI for managing clusters in style and says it provides a terminal UI that continually watches Kubernetes resources for changes.
K9s evolved around the idea that many Kubernetes workflows are repetitive inspection loops: list pods, jump to logs, describe resources, edit manifests, switch namespaces, and watch status. Its documentation grew into topics for installation, configuration, skins, plugins, benchmarks, and operational commands.
Adoption history
K9s spread through the normal cross-platform CLI packaging routes. Its official install documentation lists Homebrew and MacPorts on macOS, Linuxbrew and Pacman on Linux, and Scoop or Chocolatey on Windows, which made it easy to add to existing Kubernetes workstations.
The project reached a scale visible in repository metadata: tens of thousands of GitHub stars and thousands of forks by July 2026. That level of attention is unusual for a single-purpose terminal UI and reflects the centrality of Kubernetes day-to-day operations.
How it is used
K9s is used as an interactive cluster console. Operators open it against a kubeconfig context, watch resource tables update, drill into pods and workloads, tail logs, and trigger common commands without repeatedly composing kubectl invocations.
It complements rather than replaces kubectl: kubectl remains the scriptable primitive, while K9s is the fast human interface for scanning, debugging, and moving around clusters.
Why package nerds care
K9s is package-nerd catnip because it packages a large Kubernetes workflow into one local binary with a memorable name, broad package-manager coverage, and obvious daily utility. It is also a marker of the TUI renaissance in infrastructure tooling, alongside projects that use terminal layouts as serious operational interfaces.
Its configuration paths differ across Linux, macOS, and Windows, which makes it a useful example for package databases that track real application state rather than only executable names.
Timeline
- 2019-01: Public GitHub repository created.
- 2021: The release stream had reached the v0.24 and v0.25 series.
- 2026-07-01: Repository metadata showed more than 34,000 stars and more than 2,200 forks.
Related projects
- K9s sits beside kubectl, kubectx, kubens, Stern, Lens, OpenLens, Helm, and K8sGPT in the Kubernetes operator toolbox. Its closest conceptual relatives are terminal dashboards and resource browsers rather than deployment or package managers.
Sources
security posture
Risk level: orange
infrastructure mutation or orchestration signal.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- infrastructure mutation or orchestration signal
Signals
- text:kubernetes,cluster
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Linux
$XDG_CONFIG_HOME/k9s/config.yaml~/.config/k9s/config.yaml- macOS
~/Library/Application Support/k9s/config.yaml- Windows
%LOCALAPPDATA%\k9s\config.yaml
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
k9s | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version0.51.0
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:k9s |
|---|---|
| Version | 0.51.0 |
| Package manager | Homebrew |
| Homepage | https://k9scli.io/ |
| Repository | https://github.com/derailed/k9s |
| Last updated | 2026-07-27T21:58:35+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated agent safety answer
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation