<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on BackUpScale</title><link>https://backupscale.com/tags/networking/</link><description>Recent content in Networking on BackUpScale</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 30 Dec 2025 07:21:35 -0400</lastBuildDate><atom:link href="https://backupscale.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Drubernetes v3: Replacing Nginx Ingress with Envoy Gateway</title><link>https://backupscale.com/posts/replacing-nginx-ingress-with-envoy-gateway/</link><pubDate>Tue, 30 Dec 2025 07:21:35 -0400</pubDate><guid>https://backupscale.com/posts/replacing-nginx-ingress-with-envoy-gateway/</guid><description>&lt;p&gt;As part of contributing back to the open-source community, we maintain a Terraform module (on the Terraform Registry)&#10;for managing a Drupal site in Kubernetes. And we&amp;rsquo;re always making it more stable, both for our platform, and&#10;everyone else.&lt;/p&gt;&#10;&lt;p&gt;This release marks a significant architectural improvement: &lt;strong&gt;the transition from Nginx Ingress to Envoy Gateway&lt;/strong&gt; as the default Kubernetes ingress solution.&lt;/p&gt;&#10;&lt;p&gt;Over the years, Nginx Ingress has served the community well, but it has now reached &lt;a href="https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/"&gt;end of support and deprecation&lt;/a&gt; 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.&lt;/p&gt;</description></item></channel></rss>