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
Is your feature request related to a problem?
When attempting to update resource tags on existing load balancers, we are unable to mutate the values.
Debugging this with AWS, we determined that if the service.beta.kubernetes.io/aws-load-balancer-type value isn't set to external or nlb-ip, the load balancer controller will ignore the request. The in-tree service controller I think would modify the values, but it is passing all responsibility over to the aws-load-balancer-controller.
Describe the solution you'd like
When modifying resource tags with the aws-load-balancer-type set to nlb, the resource tags are updated, without having to recreate the nlbs.
Describe alternatives you've considered
We've considered modifying the aws-load-balancer-type to 'nlb-ip', but the documentation says this would lead to a resource leak.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When attempting to update resource tags on existing load balancers, we are unable to mutate the values.
Debugging this with AWS, we determined that if the
service.beta.kubernetes.io/aws-load-balancer-type
value isn't set toexternal
ornlb-ip
, the load balancer controller will ignore the request. The in-tree service controller I think would modify the values, but it is passing all responsibility over to the aws-load-balancer-controller.Describe the solution you'd like
When modifying resource tags with the aws-load-balancer-type set to
nlb
, the resource tags are updated, without having to recreate the nlbs.Describe alternatives you've considered
We've considered modifying the aws-load-balancer-type to 'nlb-ip', but the documentation says this would lead to a resource leak.
The text was updated successfully, but these errors were encountered: