What is Helmsman?
Helmsman is a Helm Charts (k8s applications) as Code tool which allows you to automate the deployment/management of your Helm charts from version controlled code.
How does it work?
Helmsman uses a simple declarative TOML file to allow you to describe a desired state for your k8s applications as in the example toml file. Alternatively YAML declaration is also acceptable example yaml file.
The desired state file (DSF) follows the desired state specification.
Helmsman sees what you desire, validates that your desire makes sense (e.g. that the charts you desire are available in the repos you defined), compares it with the current state of Helm and figures out what to do to make your desire come true.
To plan without executing:
$ helmsman -f example.toml
To plan and execute the plan:
$ helmsman --apply -f example.toml
To show debugging details:
$ helmsman --debug --apply -f example.toml
To run a dry-run:
$ helmsman --debug --dry-run -f example.toml
- Built for CD: Helmsman can be used as a docker image or a binary.
- Applications as code: describe your desired applications and manage them from a single version-controlled declarative file.
- Suitable for Multitenant Clusters: deploy Tiller in different namespaces with service accounts and TLS.
- Easy to use: deep knowledge of Helm CLI and Kubectl is NOT mandatory to use Helmsman.
- Plan, View, apply: you can run Helmsman to generate and view a plan with/without executing it.
- Portable: Helmsman can be used to manage charts deployments on any k8s cluster.
- Protect Namespaces/Releases: you can define certain namespaces/releases to be protected against accidental human mistakes.
- Define the order of managing releases: you can define the priorities at which releases are managed by helmsman (useful for dependencies).
- Idempotency: As long your desired state file does not change, you can execute Helmsman several times and get the same result.
- Continue from failures: In the case of partial deployment due to a specific chart deployment failure, fix your helm chart and execute Helmsman again without needing to rollback the partial successes first.
Please make sure the following are installed prior to using
Check the releases page for the different versions.
# on Linux curl -L https://github.com/Praqma/helmsman/releases/download/v1.6.2/helmsman_1.6.2_linux_amd64.tar.gz | tar zx # on MacOS curl -L https://github.com/Praqma/helmsman/releases/download/v1.6.2/helmsman_1.6.2_darwin_amd64.tar.gz | tar zx mv helmsman /usr/local/bin/helmsman
As a docker image
Check the images on dockerhub
As a package
Helmsman has been packaged in Archlinux under
helmsman-bin for the latest binary release, and
helmsman-git for master.
Documentation and How-Tos can be found here. Helmsman lets you:
- install/delete/upgrade/rollback your helm charts from code.
- work safely in a multitenant cluster.
- pass secrets/user input to helm charts from environment variables.
- send Slack notifications from Helmsman
- test releases when they are first installed.
- use public and private helm charts.
- use locally developed helm charts (the tar archives).
- define namespaces to be used in your cluster.
- move charts across namespaces.
- protect namespaces/releases against accidental changes
- Define priorities at which releases are deployed/managed
- Override the defined namespaces to deploy all releases in a specific namespace
Helmsman can be used in three different settings:
- As a binary with Minikube.
- As a binary with a hosted cluster.
- As a docker image in a CI system or local machine Always use a tagged docker image from dockerhub as the
latestimage can (at times) be unstable.
Pull requests, feedback/feature requests are welcome. Please check our contribution guide.