Update roadmap for the kubeadm LCM track

Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
pull/554/head
Bogdan Dobrelya 2016-10-18 13:44:45 +02:00
parent 1de127470f
commit 7d6fc1d680
1 changed files with 4 additions and 3 deletions

View File

@ -26,13 +26,14 @@ Kargo's roadmap
- single test with the Ansible version n-1 per day - single test with the Ansible version n-1 per day
- Test idempotency on on single OS but for all network plugins/container engines - Test idempotency on on single OS but for all network plugins/container engines
- single test on AWS per day - single test on AWS per day
- test different achitectures : - test different achitectures :
- 3 instances, 3 are members of the etcd cluster, 2 of them acting as master and node, 1 as node - 3 instances, 3 are members of the etcd cluster, 2 of them acting as master and node, 1 as node
- 5 instances, 3 are etcd and nodes, 2 are masters only - 5 instances, 3 are etcd and nodes, 2 are masters only
- 7 instances, 3 etcd only, 2 masters, 2 nodes - 7 instances, 3 etcd only, 2 masters, 2 nodes
- test scale up cluster: +1 etcd, +1 master, +1 node - test scale up cluster: +1 etcd, +1 master, +1 node
### Lifecycle ### Lifecycle
- Adopt the kubeadm tool by delegating CM tasks it is capable to accomplish well [#553](https://github.com/kubespray/kargo/issues/553)
- Drain worker node when upgrading k8s components in a worker node. [#154](https://github.com/kubespray/kargo/issues/154) - Drain worker node when upgrading k8s components in a worker node. [#154](https://github.com/kubespray/kargo/issues/154)
- Drain worker node when shutting down/deleting an instance - Drain worker node when shutting down/deleting an instance
@ -56,7 +57,7 @@ While waiting for the issue [kubernetes/kubernetes#18174](https://github.com/kub
### Kargo API ### Kargo API
- Perform all actions through an **API** - Perform all actions through an **API**
- Store inventories / configurations of mulltiple clusters - Store inventories / configurations of mulltiple clusters
- make sure that state of cluster is completely saved in no more than one config file beyond hosts inventory - make sure that state of cluster is completely saved in no more than one config file beyond hosts inventory
### Addons (with kpm) ### Addons (with kpm)
Include optionals deployments to init the cluster: Include optionals deployments to init the cluster:
@ -65,7 +66,7 @@ Include optionals deployments to init the cluster:
- **Prometheus** - **Prometheus**
##### Others ##### Others
##### Dashboards: ##### Dashboards:
- kubernetes-dashboard - kubernetes-dashboard
- Fabric8 - Fabric8