Aws-load-balancer-controller: doc about WAF annotations?

Created on 4 Mar 2019 · 6Comments · Source: kubernetes-sigs/aws-load-balancer-controller

I have set up an ALB controller and if I add WAF with AWS console, it gets removed automatically, which is the normal behavior:

disassociate WAF on arn:aws:elasticloadbalancing:eu-west-1:123454592251:loadbalancer/app/123461af-albpre-pr-04cd/1232640748b29123

The problem is that I couldn't found any documentation or information about how to configure WAF with ALB ingress controller.

Is there any WAF annotations to configure WAF?

lifecyclrotten

Source

RuBiCK

Most helpful comment

Hi，
Thanks for reporting this issue.
You can use alb.ingress.kubernetes.io/web-acl-id: yourWAFRegionalID to configure it.
That annotation is missed from the docs, will add it 😄 .

M00nF1sh on 4 Mar 2019

🎉3 👍3

All 6 comments

Hi，
Thanks for reporting this issue.
You can use alb.ingress.kubernetes.io/web-acl-id: yourWAFRegionalID to configure it.
That annotation is missed from the docs, will add it 😄 .

M00nF1sh on 4 Mar 2019

🎉3 👍3

Duplicates #608

tdmalone on 7 Mar 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 5 Jun 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 5 Jul 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 4 Aug 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.