Skip to content

Commit 7cdb175

Browse files
WAF
1 parent d27b402 commit 7cdb175

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/application-gateway/for-containers/migrate-from-agic-to-agc.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application gateway
55
author: mbender-ms
66
ms.service: azure-appgw-for-containers
77
ms.topic: concept-article
8-
ms.date: 10/28/2024
8+
ms.date: 7/22/2025
99
ms.author: mbender
1010
# Customer intent: As a Kubernetes administrator, I want to migrate services from Application Gateway Ingress Controller to Application Gateway for Containers, so that I can leverage improved performance, seamless scaling, and modern API compatibility without experiencing downtime during the transition.
1111
---
@@ -43,7 +43,6 @@ Prior to migration, it is important to identify any dependencies on Application
4343

4444
Such dependencies include:
4545

46-
- Web Application Firewall (WAF)
4746
- Private IP
4847
- Ports other than 80 and 443
4948
- Configurable request timeout values
@@ -65,7 +64,7 @@ Here's a summarized list of AGIC annotations and whether Application Gateway for
6564
| [Request timeout](migrate-from-agic-to-agc.md#request-timeout) | appgw.ingress.kubernetes.io/request-timeout | Non-configurable | Non-configurable |
6665
| [Frontend port other than 80 and 443](migrate-from-agic-to-agc.md#frontend-port-override) | appgw.ingress.kubernetes.io/override-frontend-port | Not supported | Not supported |
6766
| [Private frontend](migrate-from-agic-to-agc.md#private-frontend) | appgw.ingress.kubernetes.io/use-private-ip | Not supported | Not supported |
68-
| [WAF](migrate-from-agic-to-agc.md#waf) | appgw.ingress.kubernetes.io/waf-policy-for-path | Not supported | Not supported |
67+
| [Web Application Firewall (WAF)](migrate-from-agic-to-agc.md#waf) | appgw.ingress.kubernetes.io/waf-policy-for-path | [Web Application Firewall (WAF) (Preview)](web-application-firewall.md) | [Web Application Firewall (WAF) (Preview)](web-application-firewall.md) |
6968
| [Custom health probe](migrate-from-agic-to-agc.md#custom-health-probes) | appgw.ingress.kubernetes.io/health-probe-hostname | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) |
7069
| [Custom health probe](migrate-from-agic-to-agc.md#custom-health-probes) | appgw.ingress.kubernetes.io/health-probe-port | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) |
7170
| [Custom health probe](migrate-from-agic-to-agc.md#custom-health-probes) | appgw.ingress.kubernetes.io/health-probe-path | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) | [HealthCheckPolicy](migrate-from-agic-to-agc.md#healthcheckpolicy) |
@@ -298,7 +297,9 @@ AGIC annotation
298297
299298
Application Gateway for Containers implementation
300299
301-
WAF isn't supported by Application Gateway for Containers.
300+
#### Web Application Firewall Policy
301+
302+
For both Gateway and Ingress API, the equivalent is a new WebApplicationFirewallPolicy resource. More details can be found in the [Web Application Firewall](web-application-firewall.md) document.
302303
303304
### Custom Health probes
304305

0 commit comments

Comments
 (0)