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: articles/application-gateway/for-containers/migrate-from-agic-to-agc.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: application gateway
5
5
author: mbender-ms
6
6
ms.service: azure-appgw-for-containers
7
7
ms.topic: concept-article
8
-
ms.date: 10/28/2024
8
+
ms.date: 7/22/2025
9
9
ms.author: mbender
10
10
# 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.
11
11
---
@@ -43,7 +43,6 @@ Prior to migration, it is important to identify any dependencies on Application
43
43
44
44
Such dependencies include:
45
45
46
-
- Web Application Firewall (WAF)
47
46
- Private IP
48
47
- Ports other than 80 and 443
49
48
- Configurable request timeout values
@@ -65,7 +64,7 @@ Here's a summarized list of AGIC annotations and whether Application Gateway for
|[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 |
67
66
|[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|
|[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)|
70
69
|[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)|
71
70
|[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
298
297
299
298
Application Gateway for Containers implementation
300
299
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.
0 commit comments