I'm starting a new project in Azure Kubernetes with a greenfield approach, and I'm curious about the best ingress architecture to go with, given some specific constraints: I'm aiming for a single region deployment, I don't want to deal with any legacy Ingress APIs, and I'd prefer a built-in Web Application Firewall (WAF). I've been considering a few options:
- **Azure Application Gateway for Containers**
- **Envoy Gateway**
- **Traefik**
I'd love to hear from anyone who has experience with these, especially those using Azure Application Gateway for Containers in production. Also, if you have good references or comparisons, I'm all ears!
4 Answers
If you're looking at a straightforward solution and want to stay within Azure's ecosystem, I would recommend starting with Azure Application Gateway for Containers (AGC). The integration with WAF is seamless, and it adheres well to Gateway API standards. Just keep in mind that you're depending on Azure to keep up with feature development—it’s improving, but may need some creative workarounds for complex routing scenarios. It's a solid starting point. If you have future plans that might require more advanced configurations, consider Envoy Gateway down the line, since it offers complete control and flexibility without locking you into Azure's updates.
Honestly, if you're starting with just one cluster, AGC is the way to go. It’s simplified and effective for your needs. If you’re looking for alternatives like Envoy Gateway later on, it’s worth considering if you're okay managing your own API updates. Just an FYI, if you already have an App Gateway or Front Door in play, you might also look into the application routing add-on, though it’s still in preview.
I’ve had a good experience with AGC, it’s really straightforward and includes mTLS support and WAF, which is a plus. I've tried Traefik in the past for Docker environments and it worked well, but I wouldn’t recommend it for a fresh Azure Kubernetes setup due to its routing issues with HTTP routes. I think AGC is your safest bet initially.
There's no single right option because the choice depends on additional requirements like cost, ease of use, performance, and your own operational needs. Could be a mix of priorities. For me, AGC is appealing because of its clean integration, but I totally get the need to weigh functionality against what your application specifically needs. It’s all about finding that balance that fits your project.

Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically