Update run_in_existing_vpc.md for shared subnets tags

This commit is contained in:
Eric Hole 2017-01-24 22:02:18 -05:00 committed by GitHub
parent b3360834dc
commit ff9936fe8b
1 changed files with 2 additions and 0 deletions

View File

@ -114,6 +114,8 @@ kops update cluster ${CLUSTER_NAME}
kops update cluster ${CLUSTER_NAME} --yes
```
If you run in AWS private topology with shared subnets, and you would like Kubernetes to provision resources in these shared subnets, you must create tags on them with Key=value `KubernetesCluster=<clustername>`. This is important, for example, if your `utility` subnets are shared, you will not be able to launch any services that create Elastic Load Balancers (ELBs).
### Shared NAT Gateways
On AWS in private [topology](docs/topology.md), `kops` creates one NAT Gateway (NGW) per AZ. If your shared VPC is already set up with an NGW in the subnet that `kops` deploys private resources to, it is possible to specify the ID and have `kops`/`kubernetes` use it.