From 7b5813187cf80101e5ad2def653f3b7f19357e84 Mon Sep 17 00:00:00 2001 From: Yusuke KUOKA Date: Wed, 4 May 2016 13:22:04 +0900 Subject: [PATCH] Add documentation about `subnets` field and its subfields in `cluster.yaml` ref https://github.com/coreos/coreos-kubernetes/pull/439#discussion_r61982423 --- multi-node/aws/pkg/config/templates/cluster.yaml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/multi-node/aws/pkg/config/templates/cluster.yaml b/multi-node/aws/pkg/config/templates/cluster.yaml index 9b69edebb5..530da800a3 100644 --- a/multi-node/aws/pkg/config/templates/cluster.yaml +++ b/multi-node/aws/pkg/config/templates/cluster.yaml @@ -64,10 +64,17 @@ kmsKeyArn: "{{.KMSKeyARN}}" # CIDR for Kubernetes VPC. If vpcId is specified, must match the CIDR of existing vpc. # vpcCIDR: "10.0.0.0/16" -# CIDR for Kubernetes subnet +# CIDR for Kubernetes subnet when placing nodes in a single availability zone (not highly-available) Leave commented out for multi availability zone setting and use the below `subnets` section instead. # instanceCIDR: "10.0.0.0/24" -# IP Address for controller in Kubernetes subnet +# Kubernetes subnets with their CIDRs and availability zones. Differentiating availability zone for 2 or more subnets result in high-availability (failures of a single availability zone won't result in immediate downtimes) +# subnets: +# - availabilityZone: us-west-1a +# instanceCIDR: "10.0.0.0/24" +# - availabilityZone: us-west-1b +# instanceCIDR: "10.0.1.0/24" + +# IP Address for the controller in Kubernetes subnet. When we have 2 or more subnets, the controller is placed in the first subnet and controllerIP must be included in the instanceCIDR of the first subnet. This convention will change once we have H/A controllers # controllerIP: 10.0.0.50 # CIDR for all service IP addresses