apiVersion: k8s.mariadb.com/v1alpha1 kind: MariaDB metadata: name: mbgwp-mariadb namespace: mbgwp spec: rootPasswordSecretKeyRef: name: mbgwp-mariadb-credentials key: root-password 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 database: bitnami_wordpress username: bn_wordpress passwordSecretKeyRef: name: mbgwp-mariadb-credentials key: password storage: size: 12Gi storageClassName: longhorn resizeInUseVolumes: true waitForVolumeResize: true myCnf: | [mysqld] max_allowed_packet=64M character-set-server=utf8mb4 collation-server=utf8mb4_unicode_ci innodb_buffer_pool_size=256M innodb_log_file_size=64M max_connections=150 resources: requests: cpu: 250m memory: 512Mi limits: cpu: 1000m memory: 1Gi metrics: enabled: false updateStrategy: type: RollingUpdate