search

berops / claudie

Cloud-agnostic managed Kubernetes
https://docs.claudie.io/
Apache License 2.0
600 stars 41 forks source link

Bug: Dangling Loadbalancer infra #1521

Closed Despire closed 3 weeks ago

Despire commented 1 month ago

Current Behaviour

If a single k8s cluster has more than 1 loadbalancer attached where 1 is deleted and the other are modified and the modification fails, the deleted loadbalancer infrastructure will not get deleted, as the current state will be overwritten by the "failed" desired state.

Expected Behaviour

We should handle this edge case gracefully, where all the infra will be deleted correcly.

Steps To Reproduce

  1. Create a k8s cluster with multiple Loadbalancers attached to it.
  2. Delete one loadbalancer, modify the others.
  3. While the modification is ongoing, you can kill terraformer, to "simulate" the failure of the terraformer step.
  4. The current state will be overwritten by the state which failed, and the Loadbalancers that were supposed to be deleted will be dangling as they were not part of the desired state that was build.