Compare commits

..
Author SHA1 Message Date
renovate[bot] 2ccaea24a8 chore(deps): update helm chart mariadb-operator to v26 2026-10-26 21:54:25 +00:00
2 changed files with 2 additions and 11 deletions

No files matched your search

+1 -1
View File
@@ -13,7 +13,7 @@ spec:
source: source:
chart: mariadb-operator chart: mariadb-operator
repoURL: https://mariadb-operator.github.io/mariadb-operator repoURL: https://mariadb-operator.github.io/mariadb-operator
targetRevision: 25.10.4 targetRevision: 26.10.2
helm: helm:
values: | values: |
resources: resources:
+1 -10
View File
@@ -8,17 +8,8 @@ spec:
name: mbgwp-mariadb-credentials name: mbgwp-mariadb-credentials
key: root-password key: root-password
image: mariadb:11.8.9 image: mariadb:11.4.5
imagePullPolicy: IfNotPresent 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 port: 3306