723690c5d9
Automatic merge from submit-queue K8s 1.5 keeps container-vm as default node image on GCE There is a concern that some GCE users may be running automation that (a) turns up ephemeral clusters and (b) always uses the latest K8s release. If any of these workloads fall outside the set supported on GCI, cutting the release will break the automation. We are therefore delaying this change until we have provided sufficient warning. ```release-note K8s 1.5 keeps container-vm as the default node image on GCE for backwards compatibility reasons. Please beware that container-vm is officially deprecated and you should replace it with GCI if at all possible. You can review the migration guide here for more detail: https://cloud.google.com/container-engine/docs/node-image-migration ``` /cc @aronchick @vishh @roberthbailey
Cluster Configuration
Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Please submit new automation deployments to kube-deploy. Deployments in this directory will continue to be maintained and supported at their current level of support.
The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.
See the getting-started guides for examples of how to use the scripts.
cloudprovider/config-default.sh contains a set of tweakable definitions/parameters for the cluster.
The heavy lifting of configuring the VMs is done by SaltStack.