A declarative framework for resilient Kubernetes deployment.
Go to file
Mark Burnett b6be7f25ad Remove HAProxy reference to default namespace
Change-Id: Id42558835fd1c84a8aacfb6f5f7c2d12f57e437f
2018-05-30 14:16:47 -05:00
charts Remove HAProxy reference to default namespace 2018-05-30 14:16:47 -05:00
docs/source Bump Kubernetes version from 1.8.6 to 1.10.2 2018-05-04 09:21:18 -05:00
etc/promenade Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
examples Remove HAProxy reference to default namespace 2018-05-30 14:16:47 -05:00
promenade Update Deckhand commit 2018-05-25 11:28:13 -05:00
tests Fix DNS name list for kube services in certs 2018-02-14 15:33:41 -06:00
tools Remove HAProxy reference to default namespace 2018-05-30 14:16:47 -05:00
.dockerignore Speed up image build 2018-04-25 12:00:06 -05:00
.gitignore Report disk IO in resiliency gate 2018-02-13 12:49:44 -06:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:25:48 +01:00
.zuul.yaml Merge "Add email to docker login" 2018-05-24 20:44:56 +00:00
Dockerfile Add initial chart for Promenade API 2017-11-15 14:19:43 -06:00
LICENSE Initial commit 2017-02-14 11:13:39 -08:00
Makefile Add make tests entrypoint 2018-05-03 11:57:20 -05:00
README.md Docs: Add design doc 2017-11-16 13:50:46 -05:00
entrypoint.sh [Fix] Allow larger headers in API requests 2018-03-01 09:30:39 -06:00
requirements-direct.txt Update Deckhand commit 2018-05-25 11:28:13 -05:00
requirements-frozen.txt Update Deckhand commit 2018-05-25 11:28:13 -05:00
requirements.txt Avoid directly installing non-frozen dependencies 2017-10-20 10:54:10 -05:00
setup.py Speed up image build 2018-04-25 12:00:06 -05:00
test-requirements.txt Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
tox.ini Merge "Update Deckhand commit" 2018-05-29 13:53:29 +00:00

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 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.