Describe the bug
When setting alb.ingress.kubernetes.io/wafv2-acl-arn: none, the controller keeps retrying to associate the WEB ACL. I am trying to create the ALB for the first time.
Steps to reproduce
Set alb.ingress.kubernetes.io/wafv2-acl-arn: none
Expected outcome
It should ignore the ACL ARN association and not continuously log error.
Environment
AWS Load Balancer controller version: v2.8.1
Kubernetes version: v1.30
Using EKS (yes/no), if so version? Yes v1.30
Additional Context:
{"level":"info","ts":"2024-09-03T18:16:03Z","logger":"controllers.ingress","msg":"associating WAFv2 webACL","resourceARN":"arn:aws:elasticloadbalancing:us-east-2:XXX:loadbalancer/app/XXXX","webACLARN":"none"}
{"level":"error","ts":"2024-09-03T18:16:03Z","msg":"Reconciler error","controller":"ingress","object":{"name":"XXX"},"namespace":"","name":"XXXX","reconcileID":XXX","error":"failed to create WAFv2 webACL association on LoadBalancer: InvalidParameter: 1 validation error(s) found.\n- minimum field size of 20, AssociateWebACLInput.WebACLArn.\n"}
Describe the bug When setting
alb.ingress.kubernetes.io/wafv2-acl-arn: none
, the controller keeps retrying to associate the WEB ACL. I am trying to create the ALB for the first time.Steps to reproduce Set
alb.ingress.kubernetes.io/wafv2-acl-arn: none
Expected outcome It should ignore the ACL ARN association and not continuously log error.
Environment
Additional Context: