An orchestrator for managing a collection of Kubernetes Helm charts.
Go to file
Sean Eagan 8c5e5c7d24 Remove unused commands
This removes release rollback/delete functionality. This functionality
was likely not being used and thus was likely not working.

This primary driver for this change is to ease introduction of Helm 3
support. Particularly to avoid having to make API changes related to
the namespacing of helm releases in Helm 3.

This also removes the swagger api documentation as it was not
maintained.

Change-Id: I7edb1c449d43690c87e5bb24726a9fcaf428c00b
2021-09-30 17:22:16 -05:00
.github Add documentation to docs.airshipit.org 2020-08-03 10:33:13 +00:00
armada Remove unused commands 2021-09-30 17:22:16 -05:00
charts Remove unused commands 2021-09-30 17:22:16 -05:00
doc Remove unused commands 2021-09-30 17:22:16 -05:00
etc/armada Remove unused commands 2021-09-30 17:22:16 -05:00
examples Support builtin chart dependencies 2019-08-22 08:13:03 -05:00
hapi Move Tiller version to 2.16.9 2020-09-17 10:48:44 -05:00
images/armada Fix gates (helm install, xenial image) 2021-02-28 06:35:16 +00:00
releasenotes feat(reno): add reno 2018-06-01 21:58:18 +00:00
tools Revert "Airship 2 support features" 2021-09-30 17:22:16 -05:00
.coveragerc fix(coverage): add coverage rc file 2018-06-08 06:42:57 +00:00
.dockerignore Remove unused commands 2021-09-30 17:22:16 -05:00
.editorconfig style(armada): quality of life and cleanup 2018-02-12 10:27:11 -05:00
.gitignore Add documentation to docs.airshipit.org 2020-08-03 10:33:13 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:21 +00:00
.readthedocs.yaml Fix: Armada Exceptions docs rendering on RTD 2019-08-27 22:57:52 +02:00
.stestr.conf fix(coverage): add coverage rc file 2018-06-08 06:42:57 +00:00
.style.yapf Standardize Armada code with YAPF 2019-07-31 10:16:15 -05:00
.zuul.yaml Revert "Airship 2 support features" 2021-09-30 17:22:16 -05:00
CONTRIBUTING.rst docs(contributing): update CONTRIBUTING.rst 2018-05-21 23:58:04 +00:00
controller.sh Updating Quay Namespace to airshipit 2018-08-15 09:43:30 -05:00
entrypoint.sh images: Create single metrics dir in entrypoint 2019-10-11 10:11:16 -05:00
LICENSE Initial commit 2017-02-07 16:14:49 -08:00
Makefile Fix: Armada Exceptions docs rendering on RTD 2019-08-27 22:57:52 +02:00
plugin.yaml Bump tiller version to 2.7.2 in armada.handlers.tiller 2018-02-13 15:38:00 -05:00
README.rst Add documentation to docs.airshipit.org 2020-08-03 10:33:13 +00:00
requirements.txt Gate fixes 2021-09-30 17:21:33 -05:00
setup.cfg Add documentation to docs.airshipit.org 2020-08-03 10:33:13 +00:00
setup.py setup.py: remove executable bit 2019-09-30 11:26:52 -07:00
test-requirements.txt Gate fix for py36 2021-06-22 16:01:05 +00:00
tox.ini Standardize Armada code with YAPF 2019-07-31 10:16:15 -05:00

Armada

Docker Repository on Quay

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 in the Armada documentation.

Overview

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.

Components

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.

Installation

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:

$ sudo docker run -d --net host -p 8000:8000 --name armada \
    -v ~/.kube/config:/armada/.kube/config \
    -v $(pwd)/examples/:/examples quay.io/airshipit/armada:latest-ubuntu_bionic

Manual Installation

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

Usage

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 is one of the supported control document sources for Armada.
  • Prometheus exporter is provided for metric data related to application of charts and collections of charts. See metrics.

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

Airship.