From e0dbd0159bad4815828a22eab411c9b1bac9b8bc Mon Sep 17 00:00:00 2001 From: badaldavda8 <45222001+badaldavda8@users.noreply.github.com> Date: Fri, 11 Jan 2019 15:03:51 +0530 Subject: [PATCH] Changes in the private subnet consideration This is because for internal ELB auto subnet discovery, both tags are used - kubernetes.io/role/internal-elb 1 kubernetes.io/cluster/ shared Since as per code, first kubernetes.io/cluster/ is checked and then kubernetes.io/role/internal-elb is checked. If kubernetes.io/cluster/ is not mentioned, then internal ELB is created on Public Subnets. https://github.com/kubernetes/kubernetes/issues/29298#issuecomment-356826381 --- doc_source/network_reqs.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc_source/network_reqs.md b/doc_source/network_reqs.md index 7fe45d98..4a2fb5fc 100644 --- a/doc_source/network_reqs.md +++ b/doc_source/network_reqs.md @@ -44,4 +44,7 @@ Private subnets in your VPC should be tagged accordingly so that Kubernetes know | Key | Value | | --- | --- | -| `kubernetes.io/role/internal-elb` | `1` | \ No newline at end of file +| `kubernetes.io/role/internal-elb` | `1` | +| `kubernetes.io/cluster/` | `shared` | ++ **Key**: The ** value matches your Amazon EKS cluster's name\. ++ **Value**: The `shared` value allows more than one cluster to use this VPC\.