Engineering that ships. War stories first: incidents, migrations, benchmarks and the on-call reality behind the slides. System design, infra, Kubernetes, backend. No hype, no product pitches. Want to write for us? Open the Write for Us tab.
17+ years of IT professional experience, focused on DevOps, DevSecOps, SRE, and cloud engineering. Goal is simple to make complex concepts easy to understand
Engineering that ships. War stories first: incidents, migrations, benchmarks and the on-call reality behind the slides. System design, infra, Kubernetes, backend. No hype, no product pitches. Want to write for us? Open the Write for Us tab.
My problem with Gateway API is simpler: it is far too complicated and far too verbose for what most companies actually need. Building a gateway around it that supports modern requirements - rewrites, retries, rate limits, auth, tracing…
Thank you for this article DevOps Voice, it was very explanatory, one important note here i would mind is that ingress-nginx (specific this one, which is used by the majority of the clusters) it was retired by the maintining team in favor of NGINX…
Thanks a lot for the article. Super clear. I'm using ingress nginx in a lot of AKS and we're still deciding what to do now: another ingress controller or migrate to a more modern Gateway API.
