Limit CIDR ranges for GKE Clusters #277
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes makes new cluster support up to 256 nodes, up to 110 pods per nodes and up to 4096 services across the entire cluster. For reference, see https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips and https://cloud.google.com/architecture/gke-address-management-options#determining_the_pod_cidr_block_size
Change-Id: I0e7460c55c46677180fb0f2ef89bcc2720dd9e01