Database version upgrades about mariadb-operator

[mmontes11]

Thanks a lot!

Regarding the helm repo, I've just updated the docs pointing to the new one (https://charts.mmontes.duckdns.org ). We have some plans to improve the experience installing our chart:

• #20
• #10

MariaDB Version Tags are immutable
What is the recommanded upgrade path

That's right, this is not documented yet but the unoficial approach would be:

1. Create a MariaDB resource

apiVersion: database.mmontes.io/v1alpha1
kind: MariaDB
metadata:
  name: mariadb
spec:
  rootPasswordSecretKeyRef:
    name: mariadb
    key: root-password
  image:
    repository: mariadb
    tag: "10.7.4"
    pullPolicy: IfNotPresent
  port: 3306
  volumeClaimTemplate:
    resources:
      requests:
        storage: 100Mi
    storageClassName: standard
    accessModes:
      - ReadWriteOnce

2. Take a backup

apiVersion: database.mmontes.io/v1alpha1
kind: BackupMariaDB
metadata:
  name: backup
spec:
  mariaDbRef:
    name: mariadb
  storage:
    persistentVolumeClaim:
      resources:
        requests:
          storage: 100Mi
      storageClassName: standard
      accessModes:
        - ReadWriteOnce

3. Create a new MariaDB instance bumping the version and bootstrapping from backup:

apiVersion: database.mmontes.io/v1alpha1
kind: MariaDB
metadata:
 name: mariadb-from-backup
spec:
 rootPasswordSecretKeyRef:
   name: mariadb
   key: root-password
 image:
   repository: mariadb
   tag: "10.9.4"
   pullPolicy: IfNotPresent
 port: 3306
 volumeClaimTemplate:
   resources:
     requests:
       storage: 100Mi
   storageClassName: standard
   accessModes:
     - ReadWriteOnce
 bootstrapFromBackupRef:
   name: backup

When the new one is marked as Ready you can swap the labels in your Service to forward the traffic to it. I hope it makes sense, let me know otherwise.

We have plans to create a proper documentation with this kind of scenarios:

• #21

[mmontes11]

Closing. Please @pmig reopen if you need further help.