Kubespray’s roadmap

    • the playbook would install and configure docker and the etcd cluster
    • the following data would be inserted into etcd: certs,tokens,users,inventory,group_vars.
    • a “kubespray” container would be deployed (kubespray-cli, ansible-playbook)
    • to be discussed, a way to provide the inventory
    • self deployment of the node from inside a container

    Provisioning and cloud providers

    • On AWS autoscaling, multi AZ
    • On Azure autoscaling, create loadbalancer
    • On GCE be able to create a loadbalancer automatically (IAM ?) #280
    • TLS boostrap support for kubelet (covered by kubeadm, but not in standard deployment) (related issues: https://github.com/kubernetes/kubernetes/pull/20439 )
    • Run kubernetes e2e tests
    • Test idempotency on single OS but for all network plugins/container engines
    • single test on AWS per day
    • test scale up cluster: +1 etcd, +1 master, +1 node
    • Reorganize CI test vars into group var files

    Lifecycle

    • Upgrade granularity: select components to upgrade and skip others
    • Opencontrail
    • Consolidate roles/network_plugin and roles/kubernetes-apps/network_plugin

    Kubespray API

    • Store inventories / configurations of multiple clusters
    • Make sure that state of cluster is completely saved in no more than one config file beyond hosts inventory
    Monitoring
    • Heapster / Grafana ….
    • Prometheus
    Others
    Dashboards:
    • kubernetes-dashboard
    • Fabric8
    • Tectonic
    • Cockpit
    Paas like
    • Openshift Origin
    • Openstack
    • Deis Workflow

    Others

    • Organize and update documentation (split in categories)
    • Refactor downloads so it all runs in the beginning of deployment
    • Make bootstrapping OS more consistent
    • consul -> if officially supported by k8s
    • Flex volumes options (e.g. torrus support)
    • Clusters federation option (aka ubernetes) #329