All case studies
Cloud Architecture
Migrating 27 ingresses off a retired controller with zero downtime
Moving a fleet of ingresses from the retired ingress-nginx to F5 NGINX on the same LoadBalancer IP, with no service interruption.
- 27
- Ingresses moved
- Zero
- Downtime
- Unchanged
- LoadBalancer IP
// the challenge
A fintech running on EKS depended on the ingress-nginx controller, which was being retired. Twenty-seven ingresses had to move to a supported controller without changing public IPs or interrupting traffic.
// our approach
- Chose F5 NGINX as the supported replacement and mapped every ingress-nginx annotation to its equivalent.
- Kept the existing LoadBalancer IP so no DNS or partner allowlists had to change.
- Rolled out behind a canary with clear go/no-go checks before shifting production traffic.
- Validated all 27 ingresses end to end before decommissioning the old controller.
// the outcome
All 27 ingresses moved to a supported controller on the same IP with zero downtime, removing the risk of running on retired software while keeping every integration intact.
Have a similar challenge?
Book a 15-minute call and we'll show you where we can help — no pitch, no obligation.