-
Notifications
You must be signed in to change notification settings - Fork 145
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
fix: don't delete attached load balancers #492
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a load balancer is protected via the load-balancer-protect annotation, the load balancer will not be deleted when the service is removed. Signed-off-by: David Flanagan <david@rawkode.dev>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this looks really good.
May I ask you to extend our annotation documentation at https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/docs/controllers/services/annotations.md as well?
Yeah. I'll get that updated |
@timoreimann Should be good to go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
I'll have another look soon, thanks. |
Apologies for having dropped the ball on this one. By now, I think there are out-of-band alternatives to generally protect resources from deletion, e.g., kyverno. I'm going to close out this PR as I think the involved complexity is better managed by such tools. |
When a Load Balancer is attached via the load-balancer-id annotation,
thee CCM should not be responsible for deleting it as it was likely
provisioned by another means.
Signed-off-by: David Flanagan david@rawkode.dev
Closes #454