arya-harness
arya-harness
Could be, havent found the relevant change in NEG side yet. On a seperate note or slightly related, if we change the annotation of the service to a different neg...
My apologies, I meant that flow itself. AutoNEG is not deattaching the NEG from the GCP backend when the name of NEG is changed.
Following up on this thread a bit late, I found this issue while I was changing the NEG name. Steps to reproduce: - Create Backend Services(Global/Regional), - Create a Kubernetes...
We would really like this change as well.