<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mariadb on BackUpScale</title><link>https://backupscale.com/tags/mariadb/</link><description>Recent content in Mariadb on BackUpScale</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 21 Oct 2025 18:20:00 -0400</lastBuildDate><atom:link href="https://backupscale.com/tags/mariadb/index.xml" rel="self" type="application/rss+xml"/><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>