
Automatic merge from submit-queue Make big clusters work again after introduction of subnets This PR does two things: - make IP aliases automatically pick Node IP Range based on number of Nodes, - fix logic for starting clusters >4095 Nodes that was broken by introduction of subnets, cc @wojtek-t @shyamjvs ```release-note Setting env var ENABLE_BIG_CLUSTER_SUBNETS=true will allow kube-up.sh to start clusters bigger that 4095 Nodes on GCE. ``` Ref https://github.com/kubernetes/kubernetes/issues/47344
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.