GoogleCloudPlatform/gke-autoneg-controller

Removing config annotation does not deregister backends

soellman opened this issue · 3 comments

Removing config annotation anthos.cft.dev/autoneg still left the anthos.cft.dev/autoneg-status annotation, and also generated a controller.autoneg.dev/neg-status annotation.

I would expect autoneg to deregister backends, remove the status annotation, and remove the finalizer.

Came here to create this issue.
Just wondering what others automated process is for using the autoneg-controller? Ideally i'd like to be able to drive it via the kubectl annotate cli command. Currently this stops us from doing that.

Hi @rgardam - sorry that you're seeing this problem before we've got a chance to fix it. To fix this manually, you can kubectl edit the k8s service and remove autoneg from the list of finalizers (in metadata.finalizers).

rosmo commented

Please check the latest comment in #88.