Upgrade Percona XtraDB Cluster

Upgrade Percona XtraDB Cluster

Starting from version 1.1.0, Percona Kubernetes Operator for Percona XtraDB Cluster allows upgrades to newer versions. This includes upgrades of the Operator itself, and upgrades of the Percona XtraDB Cluster.

Upgrading the Operator

This upgrade can be done either in semi-automatic or in manual mode.

Note

The manual update mode is the recomended way for a production cluster.

Semi-automatic upgrade

Note

Only the incremental update to a nearest minor version of the Operator is supported (for example, update from 1.2.0 to 1.3.0). To update to a newer version, which differs from the current version by more than one, make several incremental updates sequentially.

  1. Update the Custom Resource Definition file for the Operator, taking it from the official repository on Github, and do the same for the Role-based access control:

    kubectl apply -f https://raw.githubusercontent.com/percona/percona-xtradb-cluster-operator/v1.5.0/deploy/crd.yaml
kubectl apply -f https://raw.githubusercontent.com/percona/percona-xtradb-cluster-operator/v1.5.0/deploy/rbac.yaml

  2. Edit the deploy/cr.yaml file, setting updateStrategy key to RollingUpdate.

  3. Now you should apply a patch to your deployment, supplying necessary image names with a newer version tag. This is done with the kubectl patch deployment command. Actual image names can be found in the list of certified images. For example, updating to the 1.5.0 version should look as follows, depending on whether you are using Percona XtraDB Cluster 5.7 or 8.0.

    1. For Percona XtraDB Cluster 5.7 run the following:

      kubectl patch deployment percona-xtradb-cluster-operator \
   -p'{"spec":{"template":{"spec":{"containers":[{"name":"percona-xtradb-cluster-operator","image":"percona/percona-xtradb-cluster-operator:1.5.0"}]}}}}'

kubectl patch pxc cluster1 --type=merge --patch '{
   "metadata": {"annotations":{ "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"pxc.percona.com/v1-5-0\"}" }},
   "spec": {"pxc":{ "image": "percona/percona-xtradb-cluster:5.7.30-31.43" },
       "proxysql": { "image": "percona/percona-xtradb-cluster-operator:1.5.0-proxysql" },
       "backup":   { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pxc5.7-backup" },
       "pmm":      { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pmm" }
   }}'

    2. For Percona XtraDB Cluster 8.0 run the following:

      kubectl patch deployment percona-xtradb-cluster-operator \
   -p'{"spec":{"template":{"spec":{"containers":[{"name":"percona-xtradb-cluster-operator","image":"percona/percona-xtradb-cluster-operator:1.5.0"}]}}}}'

kubectl patch pxc cluster1 --type=merge --patch '{
   "metadata": {"annotations":{ "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"pxc.percona.com/v1-5-0\"}" }},
   "spec": {"pxc":{ "image": "percona/percona-xtradb-cluster:8.0.19-10.1" },
       "proxysql": { "image": "percona/percona-xtradb-cluster-operator:1.5.0-proxysql" },
       "backup":   { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pxc8.0-backup" },
       "pmm":      { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pmm" }
   }}'

  4. The deployment rollout will be automatically triggered by the applied patch. You can track the rollout process in real time with the kubectl rollout status command with the name of your cluster:

    kubectl rollout status sts cluster1-pxc

Manual update

Note

Only the incremental update to a nearest minor version of the Operator is supported (for example, update from 1.2.0 to 1.3.0). To update to a newer version, which differs from the current version by more than one, make several incremental updates sequentially.

  1. Update the Custom Resource Definition file for the Operator, taking it from the official repository on Github, and do the same for the Role-based access control:

    kubectl apply -f https://raw.githubusercontent.com/percona/percona-xtradb-cluster-operator/v1.5.0/deploy/crd.yaml
kubectl apply -f https://raw.githubusercontent.com/percona/percona-xtradb-cluster-operator/v1.5.0/deploy/rbac.yaml

  2. Edit the deploy/cr.yaml file, setting updateStrategy key to OnDelete.

  3. Now you should apply a patch to your deployment, supplying necessary image names with a newer version tag. This is done with the kubectl patch deployment command. Actual image names can be found in the list of certified images. For example, updating to the 1.5.0 version should look as follows, depending on whether you are using Percona XtraDB Cluster 5.7 or 8.0.

    1. For Percona XtraDB Cluster 5.7 run the following:

      kubectl patch deployment percona-xtradb-cluster-operator \
   -p'{"spec":{"template":{"spec":{"containers":[{"name":"percona-xtradb-cluster-operator","image":"percona/percona-xtradb-cluster-operator:1.5.0"}]}}}}'

kubectl patch pxc cluster1 --type=merge --patch '{
   "metadata": {"annotations":{ "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"pxc.percona.com/v1-5-0\"}" }},
   "spec": {"pxc":{ "image": "percona/percona-xtradb-cluster:5.7.30-31.43" },
       "proxysql": { "image": "percona/percona-xtradb-cluster-operator:1.5.0-proxysql" },
       "backup":   { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pxc5.7-backup" },
       "pmm":      { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pmm" }
   }}'

    2. For Percona XtraDB Cluster 8.0 run the following:

      kubectl patch deployment percona-xtradb-cluster-operator \
   -p'{"spec":{"template":{"spec":{"containers":[{"name":"percona-xtradb-cluster-operator","image":"percona/percona-xtradb-cluster-operator:1.5.0"}]}}}}'

kubectl patch pxc cluster1 --type=merge --patch '{
   "metadata": {"annotations":{ "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"pxc.percona.com/v1-5-0\"}" }},
   "spec": {"pxc":{ "image": "percona/percona-xtradb-cluster:8.0.19-10.1" },
       "proxysql": { "image": "percona/percona-xtradb-cluster-operator:1.5.0-proxysql" },
       "backup":   { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pxc8.0-backup" },
       "pmm":      { "image": "percona/percona-xtradb-cluster-operator:1.5.0-pmm" }
   }}'

  4. The Pod with the newer Percona XtraDB Cluster image will start after you delete it. Delete targeted Pods manually one by one to make them restart in desired order:

    1. Delete the Pod using its name with the command like the following one:

      kubectl delete pod cluster1-pxc-2

    2. Wait until Pod becomes ready:

      kubectl get pod cluster1-pxc-2

      The output should be like this:

      NAME             READY   STATUS    RESTARTS   AGE
cluster1-pxc-2   1/1     Running   0          3m33s

  5. The update process is successfully finished when all Pods have been restarted.

Upgrading Percona XtraDB Cluster

Starting from version 1.5.0, the Operator can do fully automatic upgrades to the newer versions of Percona XtraDB Cluster within the method named Smart Updates.

To have this upgrade method enabled, make sure that the updateStrategy key in the deploy/cr.yaml configuration file is set to SmartUpdate.

When automatic updates are enabled, the Operator will carry on upgrades according to the following algorithm. It will query a special Version Service server at scheduled times to obtain fresh information about version numbers and valid image paths needed for the upgrade. If the current version should be upgraded, the Operator updates the CR to reflect the new image paths and carries on sequential Pods deletion in a safe order, allowing StatefulSet to redeploy the cluster Pods with the new image.

The upgrade details are set in the upgradeOptions section of the deploy/cr.yaml configuration file. Make the following edits to configure updates:

  1. Set the apply option to one of the following values:

    • Recommended - automatic upgrades will choose the most recent version of software flagged as Recommended (for clusters created from scratch, the PXC 8.0 version will be selected instead of the PCX 5.7 one regardless of the image path; for already existing clusters, the 8.0 vs. 5.7 branch choice will be preserved),

    • Latest - automatic upgrades will choose the most recent version of the software available (for clusters created from scratch, the PXC 8.0 version will be selected instead of the PCX 5.7 one regardless of the image path; for already existing clusters, the 8.0 vs. 5.7 branch choice will be preserved),

    • specific version number - will apply an upgrade if the running PXC version doesn’t match the explicit version number with no future upgrades (version numbers are specified as 5.7.26-31.37, 5.7.27-31.39, 5.7.28-31.41.2, 5.7.29-31.43, etc.),

    • Never or Disabled - disable automatic upgrades

      Note

      When automatic upgrades are disabled by the apply option, Smart Update functionality will continue working for changes triggered by other events, such as updating a ConfigMap, rotating a password, or changing resource values.

  2. Make sure the versionServiceEndpoint key is set to a valid Version Server URL (otherwise Smart Updates will not occur).

    1. You can use the URL of the official Percona’s Version Service (default). Set versionServiceEndpoint to https://check.percona.com/versions.

    2. Alternatively, you can run Version Service inside your cluster. This can be done with the kubectl command as follows:

      kubectl run version-service --image=perconalab/version-service --env="SERVE_HTTP=true" --port 11000 --expose

    Note

    Version Service is never checked if automatic updates are disabled. If automatic updates are enabled, but Version Service URL can not be reached, upgrades will not occur.

  3. Use the schedule option to specify the update checks time in CRON format.

The following example sets the midnight update checks with the official Percona’s Version Service:

spec:
  updateStrategy: SmartUpdate
  upgradeOptions:
    apply: Recommended
    versionServiceEndpoint: https://check.percona.com/versions
    schedule: "0 0 * * *"
...
Download PDF Manual

Table Of Contents

Previous topic

Pause/resume Percona XtraDB Cluster

Next topic

Scale Percona XtraDB Cluster on Kubernetes and OpenShift