AKS NGINX Ingress Migration Guide

This repository provides comprehensive guidance for migrating from NGINX Ingress Controller to alternative ingress solutions on Azure Kubernetes Service (AKS).

Background

With the deprecation of the NGINX-based Application Routing add-on in AKS, teams need to evaluate and migrate to alternative ingress solutions. This repository helps you assess your current setup and choose the best migration path for your workloads.

Repository Structure

src/
├── discover/     # Tools and scripts to detect NGINX usage in your cluster
├── agc/          # Migration guide for Azure Application Gateway for Containers
├── istio/        # Migration guide for Istio with Gateway API
├── traefik/      # Migration guide for Traefik
├── envoy/        # Migration guide for Envoy Gateway
└── kong/         # Migration guide for Kong Gateway

Getting Started

1. Discover - Assess Your Current Setup

Start with the discover directory to:

• Check if your cluster uses the Application Routing add-on
• Identify all NGINX ingress controllers in your cluster
• Find all ingress resources that will be affected
• Run automated assessment scripts

2. Choose Your Migration Path

Review the available migration options and select the one that best fits your requirements:

Azure-Native Solution

• Application Gateway for Containers (AGC) - Azure-managed, integrated with AKS, Gateway API support
• Istio - Full-featured service mesh with advanced traffic management, Gateway API support

Lightweight Ingress Controllers

• Traefik - Easy to use, automatic service discovery, Gateway API support
• Envoy Gateway - Cloud-native, high-performance, Gateway API native

API Gateway Solutions

• Kong - Feature-rich API gateway with extensive plugin ecosystem

3. Migrate - Follow Your Chosen Path

Each migration guide includes:

• Prerequisites and installation steps
• Configuration examples
• Migration strategies (side-by-side vs. blue-green)
• Testing and validation procedures
• Rollback plans

Migration Approach

All guides follow a safe migration pattern:

1. Install the new ingress solution alongside existing NGINX
2. Test with a sample application
3. Migrate services gradually (blue-green or canary)
4. Validate functionality at each step
5. Decommission NGINX once all services are migrated

Key Considerations

When choosing your migration path, consider:

• Gateway API Support - All solutions support the Kubernetes Gateway API standard
• Azure Integration - Level of integration with Azure services
• Feature Requirements - Advanced routing, security, observability needs
• Operational Complexity - Management overhead and learning curve
• Cost - Licensing, resource consumption, and Azure service costs
• Team Expertise - Existing knowledge and skills

Support and Resources

• Azure Documentation: AKS Application Routing Migration
• Gateway API: Kubernetes Gateway API

Contributing

This repository is designed to help AKS users navigate the NGINX ingress controller migration. Contributions, improvements, and feedback are welcome.

License

This project is provided as-is for guidance purposes.