Nginx Ingress to ALB Ingress Migration

Scenario Description

Migrate Kubernetes nginx Ingress resources to Alibaba Cloud ALB Ingress. ALB Ingress is a fully-managed L7 load balancer driven by three resources: a cluster-scoped AlbConfig (the ALB instance + listeners), an IngressClass bound to it, and the Ingress objects themselves.

This skill classifies every nginx.ingress.kubernetes.io/* annotation into auto-converted / behaviour-changed / unsupported, resolves unsupported annotations through a four-level decision tree (ALB-native annotation → safe to drop → ALB instance/listener-side configuration → manual work required), generates the migrated AlbConfig + IngressClass + Ingress YAML, and produces a deployment-ready migration report including the DNS weighted-cutover plan.

Architecture: nginx Ingress Controller (CLB) → ALB Ingress Controller → AlbConfig + IngressClass + Ingress → ALB instance

The core analysis workflow operates entirely offline on user-provided YAML — no cluster access, CLI tools, or cloud credentials required.

Why migrate: ACK no longer maintains the Nginx Ingress Controller component. ALB Ingress is fully managed: no operations burden and better elasticity.

Installation

This skill operates entirely offline on user-provided YAML. No CLI tools, SDKs, or cloud credentials are required.

On-demand tools (only when the workflow reaches a step that needs them):