-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Multiple security groups are created with the kubernetes.io/cluster tag #1810
Comments
related #1774 |
As a workaround adding this parameter to the module seems to do the trick:
However seeing the suggestion in that PR perhaps it's better to add it to the |
closed with #1774 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
When provisioning self_managed_node_groups with this module, multiple security groups using this module two security groups ends up being created with the
kubernetes.io/cluster/${var.cluster_name}
tag. This is a problem for at least the AWS Load Balancer Controller which fails to update some of the Target groups, logging this message:{"level":"error","ts":1643107355.1327415,"logger":"controller-runtime.manager.controller.targetGroupBinding","msg":"Reconciler error","reconciler group":"elbv2.k8s.aws","reconciler kind":"TargetGroupBinding","name":"k8s-monitor-promethe-e1f79f04c5","namespace":"monitor","error":"expect exactly one securityGroup tagged with kubernetes.io/cluster/dev for eni eni-0b6ed10e3b4d8b5c1, got: [sg-0b21ca401c50b3bad sg-0d450bf11239af6a2]"}
The security groups causing the issues seems to be these:
terraform-aws-eks/modules/self-managed-node-group/main.tf
Line 452 in 16f46db
terraform-aws-eks/node_groups.tf
Line 148 in 16f46db
Versions
Reproduction
Steps to reproduce the behaviour:
Possible workaround:
The text was updated successfully, but these errors were encountered: