An orchestrator for managing a collection of Kubernetes Helm charts.
d143c6b487
This PS adds warning-is-error = 1 under [build_sphinx] in setup.cfg so that warnings can be caught. A number of warnings/errors while building the docs are have been corrected by this PS as well. Change-Id: I445369c802e559c629a685024575bd562ea05a1b |
||
---|---|---|
.github | ||
armada | ||
docs/source | ||
etc/armada | ||
examples | ||
hapi | ||
tools | ||
.dockerignore | ||
.editorconfig | ||
.gitignore | ||
.gitreview | ||
.travis.yml | ||
CODE_OF_CONDUCT.rst | ||
CONTRIBUTING.rst | ||
controller.sh | ||
Dockerfile | ||
entrypoint.sh | ||
LICENSE | ||
OWNERS | ||
plugin.yaml | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Armada
Armada is a tool for managing multiple helm charts with dependencies by centralizing all configurations in a single Armada yaml and providing lifecycle hooks for all helm releases.
Roadmap
Detailed roadmap can be viewed here
Issues can be reported on GitHub
Installation
docker run -d --net host -p 8000:8000 --name armada -v ~/.kube/config:/armada/.kube/config -v $(pwd)/examples/:/examples quay.io/attcomdev/armada:latest
Using armada docs
Getting Started
Get started guide can be found in our Getting Started docs
Usage
Before using armada we need to check a few things:
- you have a properly configure
~/.kube/config
kubectl config view
- If it does not exist, you can create it using kubectl
- Check that you have a running Tiller
kubectl get pods -n kube-system
To run armada, simply supply it with your YAML based intention for any number of charts:
$ armada apply examples/openstack-helm.yaml [--debug-loggging ]
Your output will look something like this:
$ armada apply examples/openstack-helm.yaml 2017-02-10 09:42:36,753
armada INFO Cloning git: