[Bug]: Updating instancepool-id does not update the load balancer service

[Sapd]

Current Behavior

When editing an existing LoadBalancer service, and adjusting the instancepool id from one instacepool to another (to change it), the CCM writes "ensuring load balancer" but however does nothing.

service.beta.kubernetes.io/exoscale-loadbalancer-service-instancepool-id

It does not matter for that bug whether the load balancer is external or not. It occurs for both.

It works when one manually deletes the service inside the NLB before changing the annotation.

Expected Behavior

It should update

Steps To Reproduce

1. Create a load balancer with
   service.beta.kubernetes.io/exoscale-loadbalancer-service-instancepool-id: "A"
2. Wait until its ensured and see that it points to the instance pool with the ID A
3. Change it to
   service.beta.kubernetes.io/exoscale-loadbalancer-service-instancepool-id: "B"
4. See that it still points to A

CCM Version

v0.30.0

Kubernetes version

v1.31.0

Relevant log output

Ensured load balancer

[pierre-emmanuelJ]

Thanks for your issue, we are trying to reproduce it internally, to be able to have a patch, thanks for your issue