Arnob Kumar Saha
Zero-Downtime Migration from Ingress to Kubernetes Gateway API in ACE
The Kubernetes Gateway API is the designated successor to Ingress. It offers richer routing semantics, native TCP/UDP support, explicit timeout configuration, upstream TLS policies, and a cleaner separation between infrastructure owners and application teams — all without relying on controller-specific annotations. For kubedb-platform, migrating to Gateway API was a clear improvement. The hard part was doing it without breaking anything for our existing self-hosted users.
This post explains the three-phase strategy we used to achieve a fully transparent, zero-downtime migration.
ace
envoy-gateway
gateway-api
ingress
kubedb-platform
kubernetes
migration