Drubernetes v3: Replacing Nginx Ingress with Envoy Gateway

As part of contributing back to the open-source community, we maintain a Terraform module (on the Terraform Registry) for managing a Drupal site in Kubernetes. And we’re always making it more stable, both for our platform, and everyone else.

This release marks a significant architectural improvement: the transition from Nginx Ingress to Envoy Gateway as the default Kubernetes ingress solution.

Over the years, Nginx Ingress has served the community well, but it has now reached end of support and deprecation in the upstream ecosystem. Continued reliance on a deprecated component would limit our ability to provide secure, maintainable, and forward-looking operational patterns for Drubernetes users. To ensure long-term viability and alignment with the broader cloud native landscape, we made the strategic decision to retire Nginx Ingress from our supported stack.

In its place, we’re proud to adopt Envoy Gateway, a graduated Cloud Native Computing Federation (CNCF) project with a strong ecosystem, active community, and modern design optimized for extensibility, performance, and security. Envoy Gateway builds on the proven Envoy proxy core while offering a cloud-native ingress controller that’s well-suited for the next generation of microservices architectures.

Please see the full release notes for details.