From 794b589fcdd7107893df48d881ed54749a780b9c Mon Sep 17 00:00:00 2001 From: Marcus Johansson Date: Mon, 11 Dec 2017 18:46:56 +0100 Subject: [PATCH] Update networking.md GCP documentation has reorganized, so the existing link took us to the general VPC overview. Fixed so it links directly to the piece on routing. --- docs/concepts/cluster-administration/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cluster-administration/networking.md b/docs/concepts/cluster-administration/networking.md index e23f590765..55f52e6d3f 100644 --- a/docs/concepts/cluster-administration/networking.md +++ b/docs/concepts/cluster-administration/networking.md @@ -128,7 +128,7 @@ people have reported success with Flannel and Kubernetes. ### Google Compute Engine (GCE) For the Google Compute Engine cluster configuration scripts, we use [advanced -routing](https://cloud.google.com/compute/docs/networking#routing) to +routing](https://cloud.google.com/vpc/docs/routes) to assign each VM a subnet (default is `/24` - 254 IPs). Any traffic bound for that subnet will be routed directly to the VM by the GCE network fabric. This is in addition to the "main" IP address assigned to the VM, which is NAT'ed for