This case study walks through moving from ingress-NGINX to Envoy Gateway, including the mistakes made on the way, like nginx annotations that do not map one-to-one onto Gateway API policies.
More: https://ku.bz/mG7jhf-Q7
Post #3997
806
- Sep 25, 2026This case study explains how Modelplane was built entirely as a Crossplane configuration,…
- Sep 25, 2026This case study shows how a team ran one Kafka cluster stretched across three separate Kub…
- Sep 24, 2026This case study shows how a payments company rebuilt deployments around GitOps with Argo C…
- Sep 24, 2026This case study shows how to migrate from fragile EC2-based infrastructure to AWS EKS with…
- Sep 24, 2026This case study shows how a nightly export job kept getting OOM-killed on Kubernetes, and…
- Sep 23, 2026This case study shows how one engineer built k8s-rightsizer in four days and cut Kubernete…