Drubernetes v3 Replaces Nginx Ingress with Envoy Gateway for Modern Kubernetes Architecture

Staff Reporter

Drubernetes, the open-source platform for running Drupal in Kubernetes, has released version 3.0.0 with a major architectural upgrade, replacing Nginx Ingress with Envoy Gateway as its default ingress controller.

This change reflects a strategic shift toward modern, cloud-native infrastructure patterns. Nginx Ingress, once a staple in Kubernetes deployments, has reached end-of-support and is deprecated upstream. Continued use would pose risks around long-term maintenance, security, and ecosystem alignment.

By adopting Envoy Gateway, a graduated project under the Cloud Native Computing Foundation (CNCF), the Drubernetes team ensures the platform benefits from an actively maintained and extensible ingress solution. Built atop the Envoy proxy core, Envoy Gateway offers performance, security, and native support for microservices-based architectures, key to scaling modern Drupal applications in containerised environments.

Drubernetes is maintained by Backup Scale, which contributes back to the community through open tooling like its Terraform module for managing Drupal deployments on Kubernetes. This update aims to make the platform more stable and future-proof, not only for internal operations but also for the broader Drupal and DevOps communities using the module.

The full release notes for version 3.0.0 are available on the project’s GitLab repository.

For complete release details and to explore the updated infrastructure stack, visit the Drubernetes v3.0.0 release page.

Reference: Drubernetes v3: Replacing Nginx Ingress with Envoy Gateway by Colan Schwartz, BackUpScale (30 December 2025)

Kubernetes

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.