An orchestrator for managing a collection of Kubernetes Helm charts.
Go to file
Sean Eagan 4e0f9009a8 Implement Prometheus metric integration
This implements Prometheus metric integration, including metric
definition, collection, and exportation.

Actions measured include overall Manifest application, and Chart
application with sub-actions of download, deployment, and test.
Prometheus labels are included for Manifest and Chart name as
appropriate. Chart deployment also includes a label for which action
was taken (install, upgrade, noop).

For each of these actions, metrics are included for quantity of completed
and in progress attempts and failures, as well as the duration of the
attempts.

The API exposes these metrics via an endpoint, and the Armada chart
includes the appropriate pod annotations to configure Prometheus
scraping of this endpoint.

The CLI includes a --metrics-output option to define a path
in which to output the metric data.

Change-Id: Ia0837f28073d6cd8e0220ac84cdd261b32704ae4
2019-07-30 10:59:25 -05:00
armada Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
charts Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
doc Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
etc/armada Add viewer rule to armada API 2018-10-16 17:20:25 +00:00
examples Add chart about rabbitmq and remove timeout from example 2018-12-05 19:00:16 +08:00
hapi Revert "Move to helm 2.14" 2019-06-05 20:11:53 +00:00
images/armada Add ubuntu_xenial image build to Armada 2019-05-31 14:56:30 -05:00
releasenotes feat(reno): add reno 2018-06-01 21:58:18 +00:00
swagger test: Refactor test handler 2018-11-29 17:30:57 +00:00
tools Remove required-projects from Airskiff gate 2019-06-10 12:01:28 -05:00
.coveragerc fix(coverage): add coverage rc file 2018-06-08 06:42:57 +00:00
.dockerignore Update .dockerignore to trim image 2019-01-30 15:36:40 -06:00
.editorconfig style(armada): quality of life and cleanup 2018-02-12 10:27:11 -05:00
.gitignore Add .stestr and cover to .gitignore 2018-06-13 11:41:59 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:21 +00:00
.stestr.conf fix(coverage): add coverage rc file 2018-06-08 06:42:57 +00:00
.zuul.yaml Remove required-projects from Airskiff gate 2019-06-10 12:01:28 -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 Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
LICENSE Initial commit 2017-02-07 16:14:49 -08:00
Makefile Support armada to run on opensuse image leap15 2019-05-06 10:06:46 -07:00
plugin.yaml Bump tiller version to 2.7.2 in armada.handlers.tiller 2018-02-13 15:38:00 -05:00
README.rst Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
requirements.txt Implement Prometheus metric integration 2019-07-30 10:59:25 -05:00
setup.cfg Add airship-discuss@lists.airshipit.org 2019-01-20 11:34:57 +00:00
setup.py Adding yapf config, plus formatted code. 2018-06-22 14:56:04 -05:00
test-requirements.txt style: Pin YAPF to 0.26.0 2019-04-08 19:21:39 +00:00
tox.ini Fix bandit errors 2019-05-13 15:31:52 +02:00

Armada

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.

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 supplies storage and management of site designs and secrets.
  • Prometheus exporter is provided for metric data related to application of charts and collections of charts.

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.