<p>We are trying to test if we can have 2 or more k8s cluster in the same AWS VPC and Subnets (public and privates) using kops solution <a href="https://github.com/kubernetes/kops" rel="nofollow noreferrer">https://github.com/kubernetes/kops</a></p>

<p>We build the cluster with no issues, but when we try to expose a service through the ELB, it fails.</p>

<p>If we modify the subnet tag <code>KubernetesCluster</code> to the new cluster name, the ELB is published.</p>

<p>Is it possible to have multiple k8s cluster built with kops in the same subnets?</p>

<p>The <code>KubernetesCluster</code> tag supports multiple clusters?</p>

<p>Thanks in advance</p>

<p>Please refer to the kops <a href="https://github.com/kubernetes/kops/blob/master/docs/run_in_existing_vpc.md#shared-subnets" rel="nofollow noreferrer">documentation on shared subnets</a>:</p>

<blockquote>
  <p>If you run in AWS private topology with shared subnets, and you would
  like Kubernetes to provision resources in these shared subnets, you
  must create tags on them with Key=value
  KubernetesCluster=. This is important, for example, if
  your utility subnets are shared, you will not be able to launch any
  services that create Elastic Load Balancers (ELBs).</p>
</blockquote>

<p>Which means that yes, you will need to set the KubernetesCluster tag if you want resources that need ELBs.</p>
