<p>I have a VPC, 4 subnets (2 public and 2 private) and an EKS Cluster which all created with Terraform. My infra is working without a problem right now. I'm thinking about creating a second EKS Cluster, but I'm a little bit confused about subnet tagging.</p>
<p>For example, one of my private subnets was created like below;</p>
<pre><code>resource &quot;aws_subnet&quot; &quot;vpc-private&quot; {
  vpc_id            = aws_vpc.vpc.id
  cidr_block        = var.private_cidr
  availability_zone = data.aws_availability_zones.available.names[0]

  tags = {
    Environment                                 = var.environment
    Name                                        = &quot;${var.environment}-vpc-private&quot;
    &quot;kubernetes.io/cluster/${var.cluster_name}&quot; = &quot;shared&quot;
    &quot;kubernetes.io/role/internal-elb&quot;           = &quot;1&quot;
  }
}
</code></pre>
<p>As you can see, it's tagged with <strong>&quot;kubernetes.io/cluster/${var.cluster_name}&quot; = &quot;shared&quot;</strong> to enable subnet discovery. Since I'm thinking about creating second cluster for the same subnets, I'm trying to clarify how should subnets be tagged. There is no clear information in AWS documents, at least I didn't find anything clear about this situation. Will adding the second tag like <strong>&quot;kubernetes.io/cluster/${var.cluster_2_name}&quot; = &quot;shared&quot;</strong> be alright like below ?</p>
<pre><code>resource &quot;aws_subnet&quot; &quot;vpc-private&quot; {
  vpc_id            = aws_vpc.vpc.id
  cidr_block        = var.private_cidr
  availability_zone = data.aws_availability_zones.available.names[0]

  tags = {
    Environment                                 = var.environment
    Name                                        = &quot;${var.environment}-vpc-private&quot;
    &quot;kubernetes.io/cluster/${var.cluster_name}&quot; = &quot;shared&quot;
    &quot;kubernetes.io/cluster/${var.cluster_2_name}&quot; = &quot;shared&quot;
    &quot;kubernetes.io/role/internal-elb&quot;           = &quot;1&quot;
  }
}
</code></pre>
<p>Any help/recommendation will be highly appreciated, thank you very much.</p>

Oguzhan Aygun
<p>To answer my own question, yes tagging the subnet for each EKS Cluster is needed, otherwise load balancers couldn't find where to provision.</p>
<p>In Terraform, I used exact format I asked above</p>
<pre><code>resource &quot;aws_subnet&quot; &quot;vpc-private&quot; {
  vpc_id            = aws_vpc.vpc.id
  cidr_block        = var.private_cidr
  availability_zone = data.aws_availability_zones.available.names[0]

  tags = {
    Environment                                 = var.environment
    Name                                        = &quot;${var.environment}-vpc-private&quot;
    &quot;kubernetes.io/cluster/${var.cluster_name}&quot; = &quot;shared&quot;
    &quot;kubernetes.io/cluster/${var.cluster_2_name}&quot; = &quot;shared&quot;
    &quot;kubernetes.io/role/internal-elb&quot;           = &quot;1&quot;
  }
}
</code></pre>
