A declarative framework for resilient Kubernetes deployment.
Go to file
Felipe Monteiro b3de5e990a Promenade documentation via build_sphinx.
This PS adds tooling and automation to automatically generate
Promenade's documentation into feature-rich HTML pages that can
be hosted.

To run the documentation job, simply execute:

    tox -e docs

Change-Id: I5a925c82544c14c34c1796da5804cf12b45ae575
2017-10-06 15:06:45 -04:00
assets/etc/kubernetes/armada-loader/assets/charts Use default k8s secure port based on docs 2017-10-02 18:01:40 -05:00
docs/source Promenade documentation via build_sphinx. 2017-10-06 15:06:45 -04:00
example Support latest armada image 2017-08-24 13:42:18 -05:00
promenade Use default k8s secure port based on docs 2017-10-02 18:01:40 -05:00
tools Fix checksum issues 2017-09-18 10:40:14 -04:00
.dockerignore Basic HA kubernetes deployment (#7) 2017-06-15 20:57:22 -07:00
.gitignore Promenade documentation via build_sphinx. 2017-10-06 15:06:45 -04:00
.gitreview Add gitreview file 2017-08-11 01:18:30 -05:00
Dockerfile Update versions for testing 2017-08-16 15:07:09 -05:00
LICENSE Initial commit 2017-02-14 11:13:39 -08:00
README.md Add documentation for configuration 2017-07-03 15:36:56 -05:00
Vagrantfile Replace Virtualbox usage with KVM 2017-07-27 11:30:07 -05:00
cleanup.sh MaaS Integration Changes (#20) 2017-06-22 17:39:24 -07:00
requirements-frozen.txt Basic HA kubernetes deployment (#7) 2017-06-15 20:57:22 -07:00
requirements.txt Basic HA kubernetes deployment (#7) 2017-06-15 20:57:22 -07:00
setup.cfg Promenade documentation via build_sphinx. 2017-10-06 15:06:45 -04:00
setup.py Basic HA kubernetes deployment (#7) 2017-06-15 20:57:22 -07:00
test-requirements.txt Promenade documentation via build_sphinx. 2017-10-06 15:06:45 -04:00
tox.ini Promenade documentation via build_sphinx. 2017-10-06 15:06:45 -04:00

README.md

Promenade

Promenade is a tool for bootstrapping a resilient Kubernetes cluster and managing its life-cycle.

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.