Skip to content
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

FailedNetworkReconciling targetGroupBinding expect exactly one securityGroup tagged with kubernetes.io/cluster/<cluster_name> #3731

Open
sriramsm04 opened this issue May 31, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@sriramsm04
Copy link

sriramsm04 commented May 31, 2024

targetGroupBinding failing when both cluster_security_group_tags and node_security_group_tags have the tag kubernetes.io/cluster/<cluster_name>

Like NLB, we want to select additional tag for the controller to look for the security group if it is possible

AWS Load Balancer controller version - 2.6.2
Kubernetes version - 1.29
EKS platform version - eks.7

We are using terraform EKS blueprints to bring up our EKS cluster with both cluster and node SG. Eventually EKS is creating the kubernetes.io/cluster/<cluster_name> to both the SGs. We are using aws-load-balancer-controller add-on to create ALB and targetType as IP so while trying to add the backend SG's id to the cluster/node SG, it is failing to do so in identifying to which SG to add.

@M00nF1sh
Copy link
Collaborator

M00nF1sh commented Jun 5, 2024

/kind feature
I think we can solve this by always use the first one when multiple SG with cluster tag detected. However, this requires code change. Is possible to remove the cluster tag on the another sg of your node group?

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 5, 2024
@wweiwei-li wweiwei-li added this to the v2.9.0 milestone Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants