ALB is deleted when deletion_protection is true

[yasinlachiny]

Describe the bug
deletion_protection is on in our infra and I can see it in AWS console. But still, I can remove it at a certain condition

Steps to reproduce
Enable deletion_protection
Change scheme from internal to internet_facing from ingress in EKS
it will delete ALB and recreate it

Expected outcome
A concise description of what you expected to happen.
I expected to see some log that it can't change the scheme because deletion_protection is enabled
Environment

• AWS Load Balancer controller version:
  v2.4.4
• Kubernetes version
  1.22.12
• Using EKS (yes/no), if so version?
  yes, 1.22.12
  Additional Context:
  Is it a bug? Because when I enabled the deletion_protection I don't want to be deleted at any circumstances.

[balajisa09]

If the deletion protection is enabled from console and not as an annotation , the controller will delete the load balancer.
refer : https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/guide/ingress/annotations.md for deletion_protection annotation.

[kishorj]

@balajisa09 is correct, this is the current expected behavior if deletion protection is not specified in the annotation.

Live doc link - https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#load-balancer-attributes

[yasinlachiny]

Thank you for your response. @kishorj @balajisa09

The problem is that I enabled it via annotations in ingress. I just checked the AWS console to be sure that it's enabled.
I created a merge request based on my issue. Could you please check it?
I tested it in my env and it's working fine

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.