From 5f956433b9751a29d8c33695659deeeefb473277 Mon Sep 17 00:00:00 2001 From: Justin Santa Barbara Date: Tue, 24 Jan 2017 10:41:25 -0500 Subject: [PATCH] Document existing-subnet requirements --- docs/run_in_existing_vpc.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/run_in_existing_vpc.md b/docs/run_in_existing_vpc.md index 1ffd98dc7f..fd90c1fcba 100644 --- a/docs/run_in_existing_vpc.md +++ b/docs/run_in_existing_vpc.md @@ -135,3 +135,12 @@ spec: type: Utility zone: us-east-1a ``` + +Please note: + +* You must specify pre-create subnets for all the subnets, or for none of them. +* kops won't alter your existing subnets. Therefore they must be correctly set up with route tables etc. The + Public or Utility subnets should have public IPs and an internet gateway configured as their default route + in their route table. Private subnets should not have public IPs, and will typically have a NAT gateway + configured as their default route. +* kops won't create a route-table at all if we're not creating subnets.