From 73eb276713fabe7d5a52f0e890baf1b262482275 Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Tue, 27 Oct 2026 10:37:57 +0100 Subject: [PATCH] mbgwp: run mariadb-upgrade when MariaDB starts on 11.8 11.4 to 11.8 is a major MariaDB upgrade. MARIADB_AUTO_UPGRADE has the image's entrypoint migrate the datadir on start, as operator 26.10.1's updateStrategy.mariadbAutoUpgradeEnabled would; set as env because CI's schema for MariaDB doesn't know that field yet. --- mbgwp/mariadb-cluster.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/mbgwp/mariadb-cluster.yaml b/mbgwp/mariadb-cluster.yaml index 6b39b1e..743ae6a 100644 --- a/mbgwp/mariadb-cluster.yaml +++ b/mbgwp/mariadb-cluster.yaml @@ -10,6 +10,15 @@ spec: image: mariadb:11.8.9 imagePullPolicy: IfNotPresent + # Every X.Y is a major MariaDB release (11.4 to 11.8 too) and needs + # mariadb-upgrade on the datadir, or queries on mysql.proc fail. With this + # the image's entrypoint runs it on start; a no-op when there is nothing + # to migrate, so it stays. Operator 26.10.1 sets the same variable through + # updateStrategy.mariadbAutoUpgradeEnabled, but CI's MariaDB schema (datree + # catalog) doesn't know that field yet. + env: + - name: MARIADB_AUTO_UPGRADE + value: "true" port: 3306