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

Allow changing settings on an owned LB #533

Merged
merged 1 commit into from
Aug 26, 2022
Merged

Conversation

mikkeloscar
Copy link
Collaborator

By default adding a WAF ACL ID or a security group etc. to an ingress/routegroup would require the creation of a new load balancer. This makes sense for the cases where the load balancer is shared by multiple ingresses/routegroups but for those load balancers only owned by a single resource (via zalando.org/aws-load-balancer-shared=false) it doesn't really make sense to create a new load balancer when the setting is just adding/changing a security group, WAF ACL or the TLS settings which can be done in-place on a running LB.

This PR handles the above case so we reduce the situations where a new load balancer needs to be created.

Signed-off-by: Mikkel Oscar Lyderik Larsen <[email protected]>
@mikkeloscar mikkeloscar force-pushed the change-settings-owned-lb branch from 0448228 to b593285 Compare August 25, 2022 10:44
@szuecs
Copy link
Member

szuecs commented Aug 25, 2022

👍

1 similar comment
@mikkeloscar
Copy link
Collaborator Author

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants