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

Update run_in_existing_vpc.md 

Fixing broken links for Topology and Networking
This commit is contained in:
Justin Nauman 2017-03-15 14:05:11 -05:00 committed by GitHub
parent 103c0ed178
commit c794e139de
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/run_in_existing_vpc.md
View File

@ -80,7 +80,7 @@ but it's better to avoid the later confusion!)
### Shared Subnets
`kops` can create a cluster in shared subnets in both public and private network [topologies](topology.md). Doing so is not recommended unless you are using [external networking](docs/networking.md#supported-cni-networking)
`kops` can create a cluster in shared subnets in both public and private network [topologies](topology.md). Doing so is not recommended unless you are using [external networking](networking.md#supported-cni-networking)
After creating a basic cluster spec, edit your cluster to add the ID of the subnet:
@ -118,7 +118,7 @@ If you run in AWS private topology with shared subnets, and you would like Kuber
### 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.
On AWS in private [topology](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.
After creating a basic cluster spec, edit your cluster to specify NGW: