arkade CLI
The CLI fetches platform-specific developer tools and installs Kubernetes apps for agent-assisted environment setup.
- 4,628 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The tool installs executables and can deploy apps with the current Kubernetes context’s permissions.
Install
Manual install
curl -sLS https://get.arkade.dev | sudo shFirst Getting arkade command. The README also permits no-sudo execution with manual binary placement and provides a Git Bash route.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The tool installs executables and can deploy apps with the current Kubernetes context’s permissions.
This is third-party code. Review the repository files before installing.
What it does
arkade combines developer-tool downloads with Kubernetes app installation. The `arkade get` command fetches platform-appropriate binaries; `arkade install` deploys selected apps to a cluster. An agent can prepare versions and execute an agreed setup plan. Tools come from upstream sources and use a user directory. Apps may use Helm or other supported mechanisms, with retrievable post-install connection information.
Who it is for. Platform engineers preparing CI utilities and common apps in test Kubernetes clusters.
Good fit when
- A new runner needs several pinned CLI versions.
- An agent prepares a repeatable test-cluster environment.
- A Kubernetes app needs configuration through command flags.
- Post-install connection information needs revisiting.
Not a fit when
- The target cluster context is unknown before installation.
- Environment policy prohibits downloaded binaries.
- You expect uninstalling arkade to remove every deployed app.
Example request
Prepare a versioned CLI list for our test runner and show the arkade plan without cluster changes.Limitations
The first installer runs a downloaded script with sudo; inspect it and choose the documented route for your operating system. App deployment uses cluster access, so verify the target context and permissions before execution. Downloaded CLIs retain their own licenses and runtime requirements, which should be reviewed separately. Not every app uses Helm, so check configuration and removal procedures for the selected application.
How to disable. Stop automated arkade invocations. Manage downloaded tools and cluster apps separately; removing the command does not undo those installations.
FAQ
How do `get` and `install` differ?
`arkade get` downloads a CLI; `arkade install` deploys a Kubernetes app.
Where are downloaded tools stored?
In `~/.arkade/bin/`; include it in the appropriate PATH.
Can I select a version?
Yes. get supports a version after the tool name using @.
How do I revisit connection details?
Use `arkade info` with the app name and keep any sensitive output private.
What does Windows setup need?
The documented installer path requires Git Bash.
Discussion
No questions or reviews yet.
Related
CLI toolsA Docker sandbox for coding agents: a Debian image with Copilot CLI, Codex and Pi, and SSH, RDP and Docker enabled by flags.
A set of agents for Kubernetes and GKE: scheduled fleet audits, fixes through pull requests, replies in Google Chat and Slack
An open-source Kubernetes UI with a built-in MCP server: the agent inspects the cluster, diagnoses breakages and operates it with RBAC in mind
An AI assistant for Kubernetes that turns plain-language requests into kubectl operations and doubles as an MCP server
A Kubernetes development workflow combines image builds, deployment and source synchronization in a shared team configuration.
OpenCode agents on Kubernetes: tasks and shared settings live in manifests, and kubeoc attaches to a live agent
README in short
CLI search supports names and keywords. App-install flags can map to the relevant Helm chart settings.