You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide/ingress/annotations.md
+33-15
Original file line number
Diff line number
Diff line change
@@ -907,35 +907,53 @@ In addition, you can use annotations to specify additional tags
907
907
908
908
## Addons
909
909
910
-
!!!note
911
-
If waf-acl-arn is specified via the ingress annotations, the controller will make sure the waf-acl is associated to the provisioned ALB with the ingress.
912
-
If there is not such annotation, the controller will make sure no waf-acl is associated, so it may remove the existing waf-acl on the ALB provisioned.
913
-
If users do not want the controller to manage the waf-acl on the ALBs, they can disable the feature by setting controller command line flags `--enable-waf=false` or `--enable-wafv2=false`
914
-
915
-
- <aname="waf-acl-id">`alb.ingress.kubernetes.io/waf-acl-id`</a> specifies the identifier for the Amazon WAF web ACL.
910
+
- <aname="waf-acl-id">`alb.ingress.kubernetes.io/waf-acl-id`</a> specifies the identifier for the Amazon WAF Classic web ACL.
916
911
917
912
!!!warning ""
918
-
Only Regional WAF is supported.
913
+
Only Regional WAF Classic is supported.
914
+
915
+
!!!note ""
916
+
When this annotation is absent or empty, the controller will keep LoadBalancer WAF Classic settings unchanged.
917
+
To disable WAF Classic, explicitly set the annotation value to 'none'.
- <aname="shield-advanced-protection">`alb.ingress.kubernetes.io/shield-advanced-protection`</a> turns on / off the AWS Shield Advanced protection for the load balancer.
0 commit comments