arkade | Open Source Marketplace For Developer Tools | Continuous Deployment library

arkade downloads the correct version of a CLI for your OS and CPU. With automatic detection of: Windows / MacOS / Linux / Intel / ARM. This is a time saver compared to searching for download pages every time you need a tool. Think of arkade get TOOL as a doing for CLIs, what arkade install does for helm. Adding a new tool for download is as simple as editing tools.go.
No need to worry about whether you're installing to Intel or ARM architecture, the correct values will be set for you automatically. The post-installation message shows you how to connect. And whenever you want to see those details again, just run arkade info openfaas. There's even more options you can chose with arkade install openfaas --help - the various flags you see map to settings from the helm chart README, that you'd usually have to look up and set via a values.yaml file. If there's something missing from the list of flags that you need, arkade also supports --set for any arkade app that uses helm. Note that not every app uses helm. Remember how awkward it was last time you installed the Kubernetes dashboard? And how you could never remember the command to get the token to log in?. Forgot your token? arkade info kubernetes-dashboard. This is an example of an arkade app that uses static YAML manifests instead of helm. Prefer Portainer? Just run: arkade install portainer.
When required, tools, CLIs, and the helm binaries are downloaded and extracted to $HOME/.arkade. If installing a tool which uses helm3, arkade will check for a cached version and use that, otherwise it will download it on demand. Did you accidentally run arkade as root? Running as root is not required, and will mean your KUBECONFIG environment variable will be ignored. You can revert this using the notes on release 0.1.18.