44a0c200f2
There was a bug related to missing haproxy config files: /etc/promenade/haproxy/haproxy.cfg /etc/kubernetes/manifests/haproxy.yaml Those files are initially generated with static pods and after that it periodically updated by haproxy-anchor. Most plausible reason why it could be missed is haproxy-anchor cleaned it up while terminating. To solve the issue there were restored manually. This patch tries to make such a situation clearer by two things: 1) it leaves a message in a cleanup file that haproxy-anchor was terminated and the cleaup happened. 2) instead of removing files it moves them to backup dir from that they could be restored easily. Change-Id: Ia1449d188c15b71dd756e96b1ea2d4a672011a17 |
||
---|---|---|
charts | ||
doc/source | ||
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.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.