2e2a30515c
Daemonset update strategy defaults to OnDelete in v1beta1, whereas it defaults to RollingUpdate in v1, which seems prefereable. This also adds helm-toolkit based labels at the controller level to match standard usage such as for example by armada as wait labels. This change has been tested using the promenade resiliency gate. Change-Id: I9fd1bc4caedc0a6717b779e5333640ca8dc78b7e |
||
---|---|---|
charts | ||
doc | ||
etc/promenade | ||
examples | ||
promenade | ||
tests | ||
tools | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
README.md | ||
entrypoint.sh | ||
requirements-direct.txt | ||
requirements-frozen.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
Promenade
Promenade is a tool for bootstrapping a resilient Kubernetes cluster and managing its life-cycle via Helm charts.
Documentation can be found here.
Roadmap
The detailed Roadmap can be viewed on the OpenStack StoryBoard.
- 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 OpenStack StoryBoard.