Skip to content

Upgrade guide v0.0.26

[!NOTE]
APIs are currently in v1alpha1, which implies that non backward compatible changes might happen. See Kubernetes API versioning for more detail.

This guide illustrates, step by step, how to migrate to v0.0.26 from previous versions, as some breaking changes have been introduced in the MariaDB resource. See the changes grouped by field:

apiVersion https://github.com/mariadb-operator/mariadb-operator/pull/418

storage https://github.com/mariadb-operator/mariadb-operator/pull/407

serviceAccountName https://github.com/mariadb-operator/mariadb-operator/pull/416

galera https://github.com/mariadb-operator/mariadb-operator/pull/384 https://github.com/mariadb-operator/mariadb-operator/pull/394

Follow these steps for upgrading:

  • In your current mariadb-operator version, make sure the MariaDB to migrate is in ready state and get a copy of its manifest:

    [!IMPORTANT]
    MariaDB must be in ready state.

kubectl get mariadbs.mariadb.mmontes.io mariadb-galera -o yaml > mariadb-galera.yaml
  • Download and setup the migration script:
wget -q "https://raw.githubusercontent.com/mariadb-operator/mariadb-operator/main/hack/migrate_v0.0.26.sh"
chmod +x migrate_v0.0.26.sh
  • Install v0.0.26 CRDs:

    [!NOTE]
    Helm does not handle CRD upgrades. See helm docs.

kubectl apply --server-side=true --force-conflicts -f https://github.com/mariadb-operator/mariadb-operator/releases/download/helm-chart-0.26.0/crds.yaml
  • Execute the migration script:
./migrate_v0.0.26.sh mariadb-galera.yaml
  • Apply the v0.0.26 specification:
kubectl apply -f migrated.mariadb-galera.yaml
  • Patch the v0.0.26 status:
kubectl patch mariadbs.k8s.mariadb.com mariadb-galera --subresource status --type merge -p "$(cat status.mariadb-galera.yaml)"
  • Patch the StatefulSet ownerReferences. All the remaining children resources will be instantly recreated by the v0.0.26 operator, but you might also patch them if you want:

    [!WARNING]
    Not changing the StatefulSet ownerReferences implies that it will be garbage collected when deleting the old CRDs.

MARIADB_UID=$(kubectl get mariadbs.k8s.mariadb.com mariadb-galera -o jsonpath="{.metadata.uid}")
kubectl patch statefulset mariadb-galera --type=json -p="[
  {\"op\": \"replace\", \"path\": \"/metadata/ownerReferences/0/apiVersion\", \"value\": \"k8s.mariadb.com/v1alpha1\"}, 
  {\"op\": \"replace\", \"path\": \"/metadata/ownerReferences/0/uid\", \"value\": \"${MARIADB_UID}\"}
]"
  • Uninstall you current mariadb-operator:
helm uninstall mariadb-operator
  • If your MariaDB has Galera enabled, delete the mariadb-galera Role, as it will be specyfing the old CRDs:
kubectl delete role mariadb-galera
  • Install the current mariadb-operator version:
helm repo update mariadb-operator
helm install mariadb-operator mariadb-operator/mariadb-operator
  • Cleanup old CRDs and migration script:
OLD_HELM_VERSION=0.25.0
kubectl delete -f "https://github.com/mariadb-operator/mariadb-operator/releases/download/helm-chart-${OLD_HELM_VERSION}/crds.yaml"

rm migrate_v0.0.26.sh