diff options
| author | Di Wu <diwu1989@users.noreply.github.com> | 2017-04-01 19:50:41 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-01 19:50:41 -0700 |
| commit | c8f6752c3107d855f59cc301f8d6249f083b085d (patch) | |
| tree | 1ebf7ef2a7509042e014851cc906212ff3fadd7f | |
| parent | 4052513581bb98037309abed3151475965fcddb8 (diff) | |
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
| -rw-r--r-- | contributors/design-proposals/aws_under_the_hood.md | 4 |
1 files 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 6e3c5afb..61f00327 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 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. |