A declarative framework for resilient Kubernetes deployment.
Go to file
2019-05-01 12:24:00 +00:00
charts Merge "[fix] etcd backup to use different filename" 2019-05-01 12:24:00 +00:00
doc tools: Update Helm to v2.13.1 2019-03-28 15:22:05 +00:00
etc/promenade Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
examples Merge "Add optional external_ip to promjoin" 2019-04-25 21:25:48 +00:00
promenade Merge "Add optional external_ip to promjoin" 2019-04-25 21:25:48 +00:00
tests tools: Update Helm to v2.13.1 2019-03-28 15:22:05 +00:00
tools Merge "Add optional external_ip to promjoin" 2019-04-25 21:25:48 +00:00
.dockerignore Remove tests from images 2018-08-02 15:37:18 -05:00
.gitignore Generalize .fiotest ignore 2019-03-11 14:25:01 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:18 +00:00
.zuul.yaml Fix airship-promenade-unit-py35 gate job 2018-09-12 01:37:03 -05:00
Dockerfile Enable using PBR for package library 2018-10-25 17:04:29 -05:00
entrypoint.sh Log client-id in UCP API endpoints 2019-04-05 09:55:15 +00:00
LICENSE Initial commit 2017-02-14 11:13:39 -08:00
Makefile Minor: meaningful default label 2018-11-08 19:32:19 +01:00
README.md Update the README.md File 2018-07-30 15:52:23 -05:00
requirements-direct.txt Update Deckhand version 2019-04-18 11:28:13 -05:00
requirements-frozen.txt Update Deckhand version 2019-04-18 11:28:13 -05:00
requirements.txt Avoid directly installing non-frozen dependencies 2017-10-20 10:54:10 -05:00
setup.cfg Add airship-discuss 2019-01-15 08:27:17 +00:00
setup.py Enable using PBR for package library 2018-10-25 17:04:29 -05:00
test-requirements.txt Moving documentation only requirements into doc/requirements.txt 2019-02-11 12:11:02 +00:00
tox.ini Moving documentation only requirements into doc/requirements.txt 2019-02-11 12:11:02 +00:00

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.