-
Notifications
You must be signed in to change notification settings - Fork 733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhanced subnet discovery should use configurable tags #2904
Labels
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
Unstale |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added: The enhanced subnet discovery should use configurable tags. Currently the CNI will use any subnet in a matching VPC and AZ with the tag
kubernetes.io/role/cni: 1
. The CNI should have additional configurable tag filters.Why is this needed: If multiple EKS clusters share a VPC, they will all share subnets. It is desirable to specify additional tags unique to each cluster to limit the discovery scope. An example filter might be
kubernetes.io/cluster/my-example-cluster: shared
.kubernetes.io/role/cni
kubernetes.io/cluster/my-example-cluster
kubernetes.io/cluster/some-other-cluster
my example cluster
some other cluster
The text was updated successfully, but these errors were encountered: