Ingress-nginx is heading for end-of-life (March 2026). We built a small OSS CLI to make migrations easier:

  - Scans manifests or live clusters (multi-context, all namespaces) to find ingress-nginx usage.
  - Flags nginx classes/annotations with mapped/partial/unsupported status.
  - Generates Gateway API starter YAML (Gateway/HTTPRoute) with host/path/TLS, rewrites, redirects.
  - Optional workload scan to spot nginx/ingress-nginx images.
  - Outputs JSON reports + summary tables; CI/PR guardrail workflow included.
  - Parallel scans with timeouts; unreachable contexts surfaced.

  Quickstart:

  imk scan --all-contexts --all-namespaces --plan-output imk-plan.json --scan-images --image-filter nginx --context-timeout 30s --verbose
  imk plan --path ./manifests --gateway-dir ./out --gateway-name my-gateway --gateway-namespace default

  Binaries + source: https://github.com/ubermorgenland/ingress-migration-kit
  Feedback welcome—what mappings or controllers do you want next?