Ingress NGINX migration

Ingress NGINX is end-of-life. Are you ready?

Since March 2026 there have been no more security patches, bug fixes, or updates to Ingress NGINX. Let Digital Buttes handle the migration so your team can stay focused on shipping features.

Why us

Your operations continue while we handle the change

Minimal disruption

Your operations continue while we plan and execute the transition, with testing before every cutover.

Team stays focused

No pulling engineers off roadmap work to research controllers and troubleshoot migrations.

Right solution for you

We evaluate your setup, your annotations, and your traffic, and recommend the path that fits.

Two paths

Not sure which path to take?

We'll help you evaluate the trade-offs and make an informed decision.

Migrate to Gateway API

Adopt the current Kubernetes standard for traffic management, with more flexibility and better separation between platform and application teams.

Best for teams looking for a long-term solution.

Switch to another ingress controller

Move to a maintained alternative such as Traefik, HAProxy, or your cloud provider's controller, with minimal changes to your existing manifests.

Best for teams who want a straightforward swap.

The process

What working with us looks like

  1. 1

    Discovery

    We audit your current ingress setup and identify the custom annotations, snippets, and TLS configuration that need attention.

  2. 2

    Recommendation

    We present clear options, explain the trade-offs, and help you choose the right approach for your team.

  3. 3

    Migration

    We execute with minimal operational impact, testing thoroughly and running both controllers side by side before cutover.

  4. 4

    Handoff

    We document the new setup and walk your team through it, so the next change doesn't need us.

Let's talk about your migration

Schedule a call to discuss your current setup and figure out the best path forward.