Skip to content
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

Trying to set alb.ingress.kubernetes.io/wafv2-acl-arn to none results in a parameter validation error #4033

Open
andrewhharmon opened this issue Jan 23, 2025 · 4 comments

Comments

@andrewhharmon
Copy link

Describe the bug
I'm trying to disassociate a WAF from my ALB. The docs state you can't simply remove the annotation but must set the value to none. Upon doing that I get a reconciliation error stating the value must be larger than 20

Warning  FailedDeployModel  2m11s (x2 over 9m10s)  ingress  Failed deploy model due to failed to update WAFv2 webACL association on LoadBalancer: InvalidParameter: 1 validation error(s) found.                                                                                                                         │
 - minimum field size of 20, AssociateWebACLInput.WebACLArn.

Steps to reproduce

  • Create ALB with alb.ingress.kubernetes.io/wafv2-acl-arn set to an arn of a WAF
  • Set alb.ingress.kubernetes.io/wafv2-acl-arn to none

Expected outcome
ALB removes WAF integration

Environment

  • AWS Load Balancer controller version
    2.8.1
  • Kubernetes version
    1.31
  • Using EKS (yes/no), if so version?
    yes, eks.16

Additional Context:

@wweiwei-li
Copy link
Collaborator

Can you use alb.ingress.kubernetes.io/wafv2-acl-arn: "none"

@andrewhharmon
Copy link
Author

No, thats specifically what I tried. It doesn't seem to allow a string < 20 chars

@wweiwei-li
Copy link
Collaborator

Hey. I think I found the reason. This is a new behavior introduced in release v2.8.2, but you are still using v2.8.1

@andrewhharmon
Copy link
Author

andrewhharmon commented Jan 30, 2025

oh interesting. thanks @wweiwei-li . I will test this out today. yes I am on v2.8.1

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