
Automatic merge from submit-queue (batch tested with PRs 43177, 43202) Rename default storageclasses From UX perspective, 'default' is a bad name for the default storage class: ``` $ kubectl get storageclass NAME TYPE default (default) kubernetes.io/aws-ebs ``` This is sort of OK, it gets more confusing when user is not happy with the preinstalled default storage class and creates its own and makes it default: ``` NAME TYPE default kubernetes.io/aws-ebs iops (default) kubernetes.io/aws-ebs ``` This PR uses name of the underlying storage as name of the default storage class: ``` NAME TYPE gp2 (default) kubernetes.io/aws-ebs ``` On GCE (and many others): ``` NAME TYPE standard (default) kubernetes.io/gce-pd ``` Detailed list of names of new default storage classes: * AWS: `gp2` * GCE: `standard` (from pd-standard) * vSphere: `thin` * Cinder does not have a default - it's up to OpenStack admin to set some default and it can change at any time, using `standard` as the class name. * I was not able to find details about Azure, using `standard` too. @justinsb @jingxu97 @kerneltime @colemickens, PTAL quickly so we can catch 1.6. ```release-note NONE ``` For 1.6 release manager, this PR just renames objects in addon manager.
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.