From 0eb3f31861767463a3d231b0970a20679285747c Mon Sep 17 00:00:00 2001 From: Di Wu Date: Sat, 1 Apr 2017 19:50:41 -0700 Subject: [PATCH 1/3] Update aws_under_the_hood.md I don't think it's the POD that's getting a /24 CIDR but rather the virtual machine itself, a POD has a single address, not a range --- aws_under_the_hood.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aws_under_the_hood.md b/aws_under_the_hood.md index 6e3c5afbcc5..61f00327310 100644 --- a/aws_under_the_hood.md +++ b/aws_under_the_hood.md @@ -89,8 +89,8 @@ We do not currently run the master in an AutoScalingGroup, but we should Kubernetes uses an IP-per-pod model. This means that a node, which runs many pods, must have many IPs. AWS uses virtual private clouds (VPCs) and advanced -routing support so each pod is assigned a /24 CIDR. The assigned CIDR is then -configured to route to an instance in the VPC routing table. +routing support so each EC2 instance is assigned a /24 CIDR. The assigned CIDR +is then configured to route to an instance in the VPC routing table. It is also possible to use overlay networking on AWS, but that is not the default configuration of the kube-up script. From 3010ea8ef4f4c6795f38b34449a69f5e36238d59 Mon Sep 17 00:00:00 2001 From: Di Wu Date: Sat, 1 Apr 2017 19:52:34 -0700 Subject: [PATCH 2/3] Update aws_under_the_hood.md --- aws_under_the_hood.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aws_under_the_hood.md b/aws_under_the_hood.md index 61f00327310..43006eaf980 100644 --- a/aws_under_the_hood.md +++ b/aws_under_the_hood.md @@ -90,7 +90,7 @@ We do not currently run the master in an AutoScalingGroup, but we should Kubernetes uses an IP-per-pod model. This means that a node, which runs many pods, must have many IPs. AWS uses virtual private clouds (VPCs) and advanced routing support so each EC2 instance is assigned a /24 CIDR. The assigned CIDR -is then configured to route to an instance in the VPC routing table. +is then configured to route to that instance in the VPC routing table. It is also possible to use overlay networking on AWS, but that is not the default configuration of the kube-up script. From e3c779484233d10ab5dd8d6da76b01a572975dc4 Mon Sep 17 00:00:00 2001 From: Di Wu Date: Sat, 1 Apr 2017 19:53:21 -0700 Subject: [PATCH 3/3] Update aws_under_the_hood.md --- aws_under_the_hood.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aws_under_the_hood.md b/aws_under_the_hood.md index 43006eaf980..13ad435e544 100644 --- a/aws_under_the_hood.md +++ b/aws_under_the_hood.md @@ -89,8 +89,8 @@ We do not currently run the master in an AutoScalingGroup, but we should Kubernetes uses an IP-per-pod model. This means that a node, which runs many pods, must have many IPs. AWS uses virtual private clouds (VPCs) and advanced -routing support so each EC2 instance is assigned a /24 CIDR. The assigned CIDR -is then configured to route to that instance in the VPC routing table. +routing support so each EC2 instance is assigned a /24 CIDR in the VPC routing +table. It is also possible to use overlay networking on AWS, but that is not the default configuration of the kube-up script.