Skip to content

Preventing ALB Deletion When Deleting Ingress in EKS Cluster #4170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mphilbin88 opened this issue May 6, 2025 · 1 comment
Open

Preventing ALB Deletion When Deleting Ingress in EKS Cluster #4170

mphilbin88 opened this issue May 6, 2025 · 1 comment

Comments

@mphilbin88
Copy link

I have an EKS cluster with an ALB attached to an ingress. I've enabled deletion protection on the ALB via annotation.

However, when I delete the ingress, the ALB is also deleted. Is there a way to prevent the ALB from being deleted by EKS?

My ALB is redirecting traffic to a new endpoint, and I want to destroy the EKS cluster without destroying the ALB.

@zac-nixon
Copy link
Collaborator

Let me preface this by saying, this is not a normal procedure. However, I have confirmed my LB, TG, Listeners, SG, etc.. was preserved by doing these steps:

  1. Enable deletion protection on the ingress: alb.ingress.kubernetes.io/load-balancer-attributes: deletion_protection.enabled=true
  2. Remove the LBC finalizer ingress.k8s.aws/resources
  3. Delete the ingress, observe that AWS resources are retained while the Ingress is gone.

I didn't test with an Ingress Group, but I suspect that it might not work. Let me know if you're using an Ingress Group, and I can test that out :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants