delete.protection=true in NLB

[mo-saeed]

Right now I have ingress-nginx helm chart which uses aws load balancer controller annotations to spawn a AWS NLB and it works perfectly fine.

I have recently tried this annoation

            service.beta.kubernetes.io/aws-load-balancer-attributes: deletion_protection.enabled=true

which also works, incase by mistake I deleted the ingress-nginx service the K8s service will be protected and LB as well which is very good. the problem is the controller will not be able to reconcile this service anymore and will always show this error

2024-11-27T19:25:00.095334831Z {"level":"error","ts":"2024-11-27T19:25:00Z","msg":"Reconciler error","controller":"service","namespace":"infra-ingress","name":"ingress-nginx-controller","reconcileID":"312d073e-8780-4700-87f6-f563bd87578c","error":"deletion_protection is enabled, cannot delete the service: ingress-nginx-controller"}

Is there anyway to get aws loadbalancer controller to the first state where it can again reconcile the service as normal ?

if i changed this service.beta.kubernetes.io/aws-load-balancer-attributes: deletion_protection.enabled=true to false then it starts deleting the service with the associated LB which is a big problem in this case.

[zac-nixon]

It's not possible to reverse the deletion of the resource once it's initiated. The best we can support right with current Kubernetes limitations is to block deletion of your service until you migrate your infrastructure to a new service.