kubecm CLI
The Kubernetes configuration manager merges connections and switches contexts so agents use the intended cluster.
- 1,147 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The CLI changes kubeconfig and the active context, so later agent commands may address a different cluster.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/kubecmDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI changes kubeconfig and the active context, so later agent commands may address a different cluster.
This is third-party code. Review the repository files before installing.
What it does
kubecm organizes local Kubernetes connections. Users merge kubeconfig files and select clusters or namespaces through a menu or command. Before an agent task, they can explicitly choose the environment for subsequent operations. A Git-backed team registry describes role-based cluster sets and synchronizes local contexts. Cloud connections retrieve configuration through their providers. This distributes an agreed set of environments without manually moving every connection file.
Who it is for. Teams managing several Kubernetes clusters that need deliberate environment selection before agent tasks.
Good fit when
- An agent investigation needs a test context instead of production.
- Several received kubeconfig files must be merged.
- A user frequently switches namespaces within a cluster.
- Teams want role-based cluster sets synchronized from a registry.
Not a fit when
- The task is to provision a cluster or deploy an application.
- The user’s shared kubeconfig must not change.
- You need cluster access without the appropriate identity permissions.
Example request
Show available contexts, choose the approved test cluster and namespace, then state where subsequent commands will run.Limitations
Commands use the user kubeconfig by default, so a context switch affects subsequent Kubernetes tools as well. During registry synchronization, kubecm updates managed contexts and removes them when a cluster disappears from the role. Cloud entries need available provider credentials; the registry itself does not grant AWS or Azure permissions. Static entries can contain a complete kubeconfig, so inspect them for secrets before committing them to Git.
How to disable. Stop registry synchronization and remove the CLI if needed. Check the active context and stored connections; uninstalling the program does not undo kubeconfig edits.
FAQ
How do I choose a context from a list?
With the standalone CLI, run `kubecm switch`.
Can I switch to a known name?
Yes. Pass it to the switch command, as in `kubecm switch dev`.
How do I select a namespace?
Use `kubecm namespace` or its `kubecm ns` alias.
Can I preview registry updates?
Yes. Registry synchronization supports `--dry-run`.
Will a registry overwrite an unrelated local context?
A matching unmanaged context is skipped with a warning; registry-managed entries are updated.
Discussion
No questions or reviews yet.
Related
CLI toolsThe official Amazon EKS CLI creates and manages Kubernetes clusters from configuration that an agent can prepare for review.
The Kubernetes terminal interface shows resources and logs so users can inspect cluster state alongside agent work.
An MCP server in one binary: AI reads and edits files across several projects and runs your commands
Bitbucket CLI includes a separate read-only MCP mode, where an agent inspects one pinned context without repository-write tools.
A CLI and MCP server that use set rules to pack only the project files a task needs for the model
CCManager is a session manager for Claude Code, Codex, Gemini CLI and other agents: each runs in its own Git worktree with status and hooks
README in short
Linux, macOS and Windows are supported, with Bash, Zsh and Fish completion. Krew installs the tool as the kc plugin.