3d7c567f8c
- Tiller and helm to 2.5.0 - Kubernetes to 1.6.8 Tiller 2.5 adds a verbosity flag which we are using, so the older version not having this flag is causing test failures. Kubernetes 1.6.4 seems to not be assigning IPs to static pods, therefore they don't properly get added to services (in particular, this effects the calico-etcd service). Change-Id: I9d8a55dc2b5d248eb6bd3c820fe33f0f827bc83d |
||
---|---|---|
assets/etc/kubernetes/armada-loader/assets/charts | ||
docs | ||
example | ||
promenade | ||
tools | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
Dockerfile | ||
LICENSE | ||
README.md | ||
Vagrantfile | ||
cleanup.sh | ||
requirements-frozen.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py |
README.md
Promenade
Promenade is a tool for bootstrapping a resilient Kubernetes cluster and managing its life-cycle.
Roadmap
The detailed Roadmap can be viewed on the LCOO JIRA.
- Cluster bootstrapping
- Initial Genesis process results in a single node Kubernetes cluster with Under-cloud components deployed using Armada.
- Joining sufficient master nodes results in a resilient Kubernetes cluster.
- Destroy Genesis node after bootstrapping and re-provision as a normal node to ensure consistency.
- Life-cycle management
- Decommissioning of nodes.
- Updating Kubernetes version.
Getting Started
To get started, see getting started.
Configuration is documented here.
Bugs
Bugs are tracked in LCOO JIRA. If you find a bug, feel free to create a GitHub issue and it will be synced to JIRA.