46b6437e72
By design, the anchor pods clean up after their static pods (and associated secrets/configs) via a hook when they the anchor pods are stopped, to make sure that cruft is not left lying around (or running) when an anchor pod is no longer scheduled to a host. However, it's been observed that on a host under high load, e.g. if one or two other control plane hosts are down, then the anchor pods may be stopped in an unplanned manner. This results in service unavailability for the anchored static manifest pods. This change makes that cleanup behavior configurable (following the pattern already implemented in the haproxy chart) but leaves it on by by default. Change-Id: Iab14510ef8ea5b9e400e0f744231811117029887 |
||
---|---|---|
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.