From ed31b5b3842f351374a416c61ff24a46e2a7d245 Mon Sep 17 00:00:00 2001 From: Di Wu Date: Sat, 1 Apr 2017 19:53:21 -0700 Subject: [PATCH] Update aws_under_the_hood.md --- contributors/design-proposals/aws_under_the_hood.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributors/design-proposals/aws_under_the_hood.md b/contributors/design-proposals/aws_under_the_hood.md index 43006eaf9..13ad435e5 100644 --- a/contributors/design-proposals/aws_under_the_hood.md +++ b/contributors/design-proposals/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.