You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the guides to launch a k8s cluster with a p4de instance and I think the default security groups it created had two groups with the kubernetes.io/cluster/k8s-gpu-cluster tag included. When trying to later create an ingress load balancer using the aws load balancer controller, the loadbalancer failed to configure everything.
This matches this error report and deleting the tag in one security group resolved the issue.
It'd be very helpful to figure out where this double tagging is happening and add a fix so that eks clusters are well configured for load balancers.
The text was updated successfully, but these errors were encountered:
I followed the guides to launch a k8s cluster with a p4de instance and I think the default security groups it created had two groups with the
kubernetes.io/cluster/k8s-gpu-cluster
tag included. When trying to later create an ingress load balancer using the aws load balancer controller, the loadbalancer failed to configure everything.This matches this error report and deleting the tag in one security group resolved the issue.
It'd be very helpful to figure out where this double tagging is happening and add a fix so that eks clusters are well configured for load balancers.
The text was updated successfully, but these errors were encountered: