Posted in

Application Gateway for Containers Migration Utility

🔹 Feature: Application Gateway for Containers Migration Utility
🔹 What It Does: Auto-converts existing AGIC and NGINX Ingress resources into Gateway API YAML for Application Gateway for Containers.

What Is It Giving You:

✅ Read-Only, Non-Destructive: Scan files OR a live cluster. The utility never modifies your existing ingresses or workloads — it only generates Gateway API YAML for you to review and apply when ready.
✅ Two Input Modes: files mode reads YAML manifests from disk; cluster mode reads Ingress resources directly from your cluster using the current kubeconfig context.
✅ Two Provider Sources: agic (default) migrates AGIC annotations; nginx migrates NGINX Ingress Controller annotations. One tool, both migration paths.
✅ Detailed Migration Report: Per-annotation status — completed, warning, not-supported, error — plus actionable recommendations for anything that requires manual steps.
✅ Flexible Output: Print to stdout, single file, or a directory with one file per resource. Pipe straight into GitOps.
✅ BYO or ALB-Controller Managed: Point at an existing AGC via –byo-resource-id, or generate an ApplicationLoadBalancer custom resource with –managed-subnet-id so the ALB Controller provisions and manages AGC for you.
✅ Cross-Platform Binaries: Linux, macOS, Windows (amd64 + arm64) — build once with ./build.sh.

🌐 https://github.com/Azure/Application-Gateway-for-Containers-Migration-Utility

Microsoft Certified Trainer, Office 365, AWS, Azure and Cloud Expert-Architect. In the IT world for over than 20 years.

Apart from the main area of Microsoft Azure expert in the field of infrastructure servers Windows Server 2003-2019, Microsoft Active Directory, Hyper-V Private Cloud, IIS, System Center, SQL.

Private Cloud, System Center, Hyper-V, Open Stack Expert and all Microsoft products Expert. Linux Server administrator.

My Azure community projects:

https://mazeball.azurewebsites.net/
https://github.com/MariuszFerdyn?tab=repositories

More