Closed marianhromiak closed 11 months ago
The NEGs are created by the cloud.google.com/neg
annotation by GKE itself, Autoneg just adds these to a backend service. So it's more of an GKE issue I'd say...
Ah, sorry, I did not see that these were not getting detached - let me have a look at this.
Hi @rosmo, Do you know if there is any progress? 🙏 We switched to the autoneg-controller from the custom-controlled NEGs attachment, which works great. We have a very dynamic environment, and the cleanup after the deletion process is painful. We would expect the controller to handle it all end-to-end. Thanks!
Hi, We have also encountered this issue. would love to know if this is worked on. Thanks 🙏
I'll try to find some time soon, but always happy to receive patches!
Can you give the new 0.9.10 release a try?
seems to work correctly in 0.9.10, thanks
I'm having issue with the autoneg v0.9.9. Everything seems to be working fine since I deleted service with
autoneg
annotations.I can see deregistering message in logs
but these NEGs will never be deleted or detached from backend service.
Is there anything what can I check why these NEGs persist service deletion, or is there cook book how to correct delete service with NEG annotation?