Last activity 11h agoPosted Nov 26, 2025 at 10:15 AM EST

Ingress Migration Kit (imk): Audit Ingress-Nginx and Migrate Before Eol

random_round

1 points

1 comments

Mood

informative

Sentiment

positive

Discussion Activity

Light discussion

First comment

N/A

Peak period

Hour 1

Avg / period

Key moments

01Story posted
Nov 26, 2025 at 10:15 AM EST
11h ago
Step 01
02First comment
Nov 26, 2025 at 10:15 AM EST
0s after posting
Step 02
03Peak activity
1 comments in Hour 1
Hottest window of the conversation
Step 03
04Latest activity
Nov 26, 2025 at 10:15 AM EST
11h ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (1 comments)

Showing 1 comments

random_roundAuthor

11h ago

  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?

View full discussion on Hacker News

ID: 46058161Type: storyLast synced: 11/26/2025, 3:16:08 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Read Article View on HN

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?