<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructureautomation on BackUpScale</title><link>https://backupscale.com/tags/infrastructureautomation/</link><description>Recent content in Infrastructureautomation 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/infrastructureautomation/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><item><title>Announcing Drubernetes v2: Moving from Bitnami to the Official MariaDB Operator</title><link>https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/</link><pubDate>Tue, 21 Oct 2025 18:20:00 -0400</pubDate><guid>https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;Bitnami’s licensing and support changes have made its once-free Helm charts unsustainable for open-source projects. In response, &lt;a href="https://gitlab.com/backupscale/drubernetes"&gt;Drubernetes&lt;/a&gt;, &lt;strong&gt;the Terraform module for running Drupal on Kubernetes&lt;/strong&gt;, has replaced Bitnami’s MariaDB chart with the official MariaDB operator in its 2.0.0 release to ensure continued open-source compatibility, security, and portability. This release requires a few migration steps, including backing up your current Drupal database (DB), applying the latest Drubernetes code to your infrastructure, and then restoring your DB, which will bring you a cleaner, more future-proof architecture.&lt;/p&gt;</description></item></channel></rss>