alibabacloud-nginx-ingress-to-api-gateway

Migrate Nginx Ingress to APIG by analyzing your YAML to classify nginx.ingress.kubernetes.io annotations, mapping compatible rules to Higress features, and outputting migrated YAML with ingressClassName set to apig.

Unsupported annotations are removed or mapped to WasmPlugin configurations during migration. The skill classifies annotations into Compatible, Ignorable, and Unsupported categories, preserving valid rules while annotating unsupported ones with wasmplugin as needed.

Yes, you can analyze Ingress YAML offline to generate a deployment-ready migration report. The process operates entirely on your provided YAML, producing compatibility analysis, migrated Ingress YAMLs, and post-migration verification guidance.

WasmPlugin extends Higress by replacing unsupported Nginx Ingress annotations with custom Wasm plugins. The migration logic decides which annotations require WasmPlugin implementation and annotates the migrated YAML accordingly to retain original routing behaviors.

Migrating Ingress to API Gateway preserves your existing TLS and routing rules. The skill generates migrated YAML that retains original traffic rules and TLS configurations while changing the ingressClassName to apig and stripping incompatible annotations.

The best way to classify Nginx Ingress annotations for APIG compatibility is to use an automated migration tool that evaluates each annotation against Higress native features, categorizing them as Compatible, Ignorable, or Unsupported for accurate YAML conversion.