A declarative framework for resilient Kubernetes deployment.
Go to file
Mark Burnett 0a5c68ffbf Uplift CoreDNS from 1.0.5 to 1.1.2
Also switch to using the forward plugin for upstream servers.

Change-Id: I91d89fc28384e47444c0c35683a0accf81a4695d
2018-05-02 14:21:50 -05:00
charts Uplift CoreDNS from 1.0.5 to 1.1.2 2018-05-02 14:21:50 -05:00
docs/source Allow adding new definitions to PKICatalog 2018-05-01 14:01:03 +00:00
etc/promenade Minor testing-related cleanup 2018-01-02 10:14:10 -06:00
examples Uplift CoreDNS from 1.0.5 to 1.1.2 2018-05-02 14:21:50 -05:00
promenade Merge "Add a second auxiliary etcd server for bootstrap" 2018-05-01 21:41:28 +00:00
tests Fix DNS name list for kube services in certs 2018-02-14 15:33:41 -06:00
tools Uplift CoreDNS from 1.0.5 to 1.1.2 2018-05-02 14:21:50 -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 Add gitreview file 2017-08-11 01:18:30 -05: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 Missing resource limits on apiserver pod 2018-04-03 10:15:29 -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 Bump Deckhand version 2018-04-05 11:37:45 -05:00
requirements-frozen.txt Bump Deckhand version 2018-04-05 11:37:45 -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 Speed up image build 2018-04-25 12:00:06 -05: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.