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
We specify the annotation service.beta.kubernetes.io/aws-load-balancer-type: "external" in Service as a Load Balancer to let latest version of AWS LBC controller pick the resource and provision a nlb instead of classic.
However, when applying the same annotation in Gateway Resource, its still deploying classic load balancer which indicates that this annotation is not taking effect.
Could you please help with the correct annotation to be used with Gateway Resource to be able to let latest version of AWS LBC controller to pick the resource and provision a nlb?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We specify the annotation service.beta.kubernetes.io/aws-load-balancer-type: "external" in Service as a Load Balancer to let latest version of AWS LBC controller pick the resource and provision a nlb instead of classic.
However, when applying the same annotation in Gateway Resource, its still deploying classic load balancer which indicates that this annotation is not taking effect.
Could you please help with the correct annotation to be used with Gateway Resource to be able to let latest version of AWS LBC controller to pick the resource and provision a nlb?
Beta Was this translation helpful? Give feedback.
All reactions