An orchestrator for managing a collection of Kubernetes Helm charts.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 07b4f61c05 Merge "Prevent tiller from leaving releases in pending status" 3 days ago
armada Fix unauthenticated requests to create locks 1 week ago
charts Merge "Prevent tiller from leaving releases in pending status" 3 days ago
doc Merge "Support armada to run on opensuse image leap15" 1 month ago
etc/armada Add viewer rule to armada API 8 months ago
examples Add chart about rabbitmq and remove timeout from example 6 months ago
hapi Revert "Move to helm 2.14" 2 weeks ago
images/armada Add ubuntu_xenial image build to Armada 2 weeks ago
releasenotes feat(reno): add reno 1 year ago
swagger test: Refactor test handler 6 months ago
tools Remove required-projects from Airskiff gate 1 week ago
.coveragerc fix(coverage): add coverage rc file 1 year ago
.dockerignore Update .dockerignore to trim image 4 months ago
.editorconfig style(armada): quality of life and cleanup 1 year ago
.gitignore Add .stestr and cover to .gitignore 1 year ago
.gitreview OpenDev Migration Patch 2 months ago
.stestr.conf fix(coverage): add coverage rc file 1 year ago
.zuul.yaml Remove required-projects from Airskiff gate 1 week ago
CONTRIBUTING.rst docs(contributing): update CONTRIBUTING.rst 1 year ago
LICENSE Initial commit 2 years ago
Makefile Support armada to run on opensuse image leap15 1 month ago
README.rst Support armada to run on opensuse image leap15 1 month ago Updating Quay Namespace to airshipit 10 months ago api: Update entrypoint script with proper quotes 8 months ago
plugin.yaml Bump tiller version to 2.7.2 in armada.handlers.tiller 1 year ago
requirements.txt Move to kubernetes python client 9.0.0 2 months ago
setup.cfg Add 5 months ago Adding yapf config, plus formatted code. 1 year ago
test-requirements.txt style: Pin YAPF to 0.26.0 2 months ago
tox.ini Fix bandit errors 1 month ago



Docker Repository on Quay Doc Status

Armada is a tool for managing multiple Helm charts with dependencies by centralizing all configurations in a single Armada YAML and providing life-cycle hooks for all Helm releases.

Find more documentation for Armada on Read The Docs.


The Armada Python library and command line tool provide a way to synchronize a Helm (Tiller) target with an operator's intended state, consisting of several charts, dependencies, and overrides using a single file or directory with a collection of files. This allows operators to define many charts, potentially with different namespaces for those releases, and their overrides in a central place. With a single command, deploy and/or upgrade them where applicable.

Armada also supports fetching Helm chart source and then building charts from source from various local and remote locations, such as Git endpoints, tarballs or local directories.

It will also give the operator some indication of what is about to change by assisting with diffs for both values, values overrides, and actual template changes.

Its functionality extends beyond Helm, assisting in interacting with Kubernetes directly to perform basic pre- and post-steps, such as removing completed or failed jobs, running backup jobs, blocking on chart readiness, or deleting resources that do not support upgrades. However, primarily, it is an interface to support orchestrating Helm.


Armada consists of two separate but complementary components:

  1. CLI component (mandatory) which interfaces directly with Tiller.
  2. API component (optional) which services user requests through a wsgi server (which in turn communicates with the Tiller server) and provides the following additional functionality:
    • Role-Based Access Control.
    • Limiting projects to specific Tiller functionality by leveraging project-scoping provided by Keystone.


Quick Start (via Container)

Armada can be most easily installed as a container, which requires Docker to be executed. To install Docker, please reference the following install guide.

Afterward, you can launch the Armada container by executing:

Manual Installation

For a comprehensive manual installation guide, please see Manual Install Guide.


To run Armada, simply supply it with your YAML-based intention for any number of charts:

$ armada apply examples/openstack-helm.yaml [ --debug ]

Which should output something like this:

$ armada apply examples/openstack-helm.yaml 2017-02-10 09:42:36,753

  armada INFO Cloning git:

For more information on how to install and use Armada, please reference: Armada Quickstart.

Integration Points

Armada CLI component has the following integration points:

  • Tiller manages Armada chart installations.
  • Deckhand supplies storage and management of site designs and secrets.

In addition, Armada's API component has the following integration points:

  • Keystone (OpenStack's identity service) provides authentication and support for role-based authorization.

Further Reading