End of support for WAF Classic

[alebedev87]

I noticed that github.com/aws/aws-sdk-go-v2/service/wafregional package cannot create WAF Classic ACLs anymore reporting the following error:

WAFBadRequestException: AWS WAF Classic (v1) support will end on September 30, 2025. Effective May 1st, 2025, the creation of new WebACL v1 is no longer permitted.

Looks like AWS is going to end the support of WAF Classic in September 2025. However, the usage of WAF Classic seems to be impossible already.

Do we plan to deprecate the support of --enable-waf flag?

[wweiwei-li]

Thanks for bringing this up. We are aware of this, and will plan on deprecate the support of --enable-waf flag

[alebedev87]

@wweiwei-li : Thank you for a quick reply! Do you have any deadlines for the deprecation? It seems that WAF Classic Web ACLs cannot be created anymore (even if the date mentioned is 30SEP2025). Which makes the usage of --enable-waf and alb.ingress.kubernetes.io/waf-acl-id annotation impossible.

[kellyyan]

@alebedev87 Hi, we don't have a timeline for deprecation. Yes, WAF Classic Web ACLs cannot be created anymore. We will continue to monitor this issue.

[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

[alebedev87]

/remove-lifecycle stale