From 17c18d1103d55a7b8801e138d6cd54910165acc9 Mon Sep 17 00:00:00 2001 From: Jon Chiu Date: Sat, 4 Mar 2017 23:54:03 -0800 Subject: [PATCH] Document kubenet and --topology private --- docs/networking.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/networking.md b/docs/networking.md index c3701d6353..0e2e2f2f8f 100644 --- a/docs/networking.md +++ b/docs/networking.md @@ -22,6 +22,10 @@ routing table, and thus it requires its own subnet. It is theoretically possibl with other infrastructure (but not a second cluster!), but this is not really recommended. Certain `cni` networking solutions claim to address these problems. +Users running `--topology private` will not be able to choose `kubenet` networking because `kubenet` +requires a single routing table. These advanced users are usually running in multiple availability zones +and NAT gateways are single AZ, multiple route tables are needed to use each NAT gateway. + ### Supported CNI Networking Several different providers are currently built into kops: