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
Currently, if you have only AWS Managed nodegroups, the ELB traffic is not able of reaching them, because the ASG created by AWS doesn't have the ELB Target group added, we have to create "aws_autoscaling_attachment" resource to add it.
Why didn't we realized of this before?
Because we always use a custom nodegroup which is actually added as a ELB target group, so the kubernetes kube-proxy does the work of re-route the traffic for them
The text was updated successfully, but these errors were encountered:
Currently, if you have only AWS Managed nodegroups, the ELB traffic is not able of reaching them, because the ASG created by AWS doesn't have the ELB Target group added, we have to create
"aws_autoscaling_attachment"
resource to add it.Why didn't we realized of this before?
Because we always use a custom nodegroup which is actually added as a ELB target group, so the kubernetes kube-proxy does the work of re-route the traffic for them
The text was updated successfully, but these errors were encountered: