Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove workstreams from scope and objectives #948

Merged
merged 1 commit into from
May 16, 2019
Merged

Remove workstreams from scope and objectives #948

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 0 additions & 22 deletions docs/scope-and-objectives.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,25 +143,3 @@ As a result, existing popular deployment mechanisms that manage Kubernetes clust
- 🔌 Cluster API MUST provide the ability to receive the health status of a Kubernetes Node from an external source.

- 🔌 Cluster API provider implementations SHOULD allow customization of machine, node, or operating system image.

## Workstreams

After the release of v1alpha1 and scoped down the project's requirements, the project contributors and maintainers defined the following workstreams.

Each workstream should produce one or more CAEP(s) to be merged in [proposals](./proposals) and proceed to implementation phase afterwards.

#### extension-mechanism — [Minutes](https://docs.google.com/document/d/1Wb1FUZTixi9wzEEN_Ch00cLJPFdXmq9ZMFTitAQiJls/edit#heading=h.atlkbr6lt6hh)

Define how Cluster API interact with infrastructure providers.

#### data-model — [Minutes](https://docs.google.com/document/d/1R5OTjLzGk2-KdcfD1eeMO_O_21d3acKAaGnbqpUmabw/edit#heading=h.atlkbr6lt6hh)

Define new types or redefine existing ones focusing on defining high level concepts as well as drawing boundaries and responsibilities.

#### controlplane-lifecycle-management — [Minutes](https://docs.google.com/document/d/1hTDKdWXTHUwm_G2OSXCNoI-FO1L5E825bJpY7D_u6CM/edit#heading=h.atlkbr6lt6hh)

Make the cluster control plane a first class resource, support control plane lifecycle actions such as scaling or upgrades.

#### node-lifecycle-management — [Minutes](https://docs.google.com/document/d/1E7N_JcSsDnnJk2yqMCCriBFwRZZc8nnx4kxSt99z7As/edit#heading=h.atlkbr6lt6hh)

Define the extension points for bootstrapping control plane and non control plane nodes. Provide a reference implementation using `kubeadm`. Figure out implementations with cluster autoscaler.