kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1615 from geojaz/patch-1 

Update run_in_existing_vpc.md note for tagging shared subnets
This commit is contained in:
Chris Love 2017-01-28 21:56:30 -07:00 committed by GitHub
parent bb179bb8cb ff9936fe8b
commit 58b92bc390
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/run_in_existing_vpc.md
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.