This change introduces a configuration option to control whether Tiller listens on any IP addresses (the previous default), or binds only to 127.0.0.1 (the new default). The same option is used for both the Armada and Tiller charts: .conf.tiller.listen_on_any (default: false) The affected tiller command line argument is: -listen 127.0.0.1:port (if false) -listen :port (if true) Listening on any address allows Helm client direct access to Tiller, via 'helm --host pod_ip:port'. Listening on localhost does prevent connections directly to the pod IP, but it does not preclude the use of 'kubectl port-forward' to establish a connection to Tiller. The Tiller container in the Armada pod exists only to service Armada via 127.0.0.1. The Helm client automatically sets up port forwarding (if it has access to the Kubernetes API). As a result, this change should be non-impacting. However, the previous behavior can be restored by setting .conf.tiller.listen_on_any=true. Change-Id: Id308976bac21cc521e8470516ce49ebd1942da68
|3 weeks ago|
|.github||9 months ago|
|armada||2 months ago|
|charts||3 weeks ago|
|doc||9 months ago|
|etc/armada||3 years ago|
|examples||2 years ago|
|hapi||8 months ago|
|images/armada||3 months ago|
|manifests||1 year ago|
|releasenotes||3 years ago|
|swagger||2 years ago|
|tools||3 months ago|
|.coveragerc||3 years ago|
|.dockerignore||2 years ago|
|.editorconfig||3 years ago|
|.gitignore||9 months ago|
|.gitreview||2 years ago|
|.readthedocs.yaml||2 years ago|
|.stestr.conf||3 years ago|
|.style.yapf||2 years ago|
|.zuul.yaml||9 months ago|
|CONTRIBUTING.rst||3 years ago|
|LICENSE||4 years ago|
|Makefile||2 years ago|
|README.rst||9 months ago|
|controller.sh||3 years ago|
|entrypoint.sh||2 years ago|
|plugin.yaml||3 years ago|
|requirements.txt||8 months ago|
|setup.cfg||9 months ago|
|setup.py||3 years ago|
|test-requirements.txt||8 months ago|
|tox.ini||2 years ago|
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.
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:
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:
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.
Armada CLI component has the following integration points:
In addition, Armada's API component has the following integration points:
- Keystone (OpenStack's identity service) provides authentication and support for role-based authorization.