Perform an Upgrade

As new versions of the Kubernetes API are released, some of these object manifests will need to be updated to match the updates to the Kubernetes API. When upgrading the Kubernetes version and the Operator, SingleStore recommends updating all of these object definitions to ensure that they are utilizing the proper Kubernetes API version for these objects.

SingleStore recommends upgrading one component at a time.

Upgrade the Operator

Note

Please confirm that the cluster is stable before performing the upgrade.

Typically, upgrading the Operator will not cause the cluster to restart or change.

Edit the sdb-operator.yaml file and update spec.template.spec.containers[0].image with a later version of Operator image.

Note: When upgrading from Operator 1.2.5 or earlier, be sure to include the required --cluster-id field and a value to this file. Refer to the sdb-operator.yaml file for additional information.
Apply the upgrade.
Shell
```
kubectl apply -f sdb-operator.yaml
```

Upgrade the SingleStoreDB Engine

Note

To upgrade to SingleStoreDB version 8.1 and later, you must first upgrade the Operator to version 3.40.3 or later.

Please confirm that the cluster is stable before performing the upgrade. Reviewing the Operator log to confirm that there are no general Operator operations in progress is recommended.

Edit the sdb-cluster.yaml file and replace spec.nodeImage.repository and spec.nodeImage.tag with a later version of the node image.
Apply the upgrade.
Shell
```
kubectl apply -f sdb-cluster.yaml
```

Should an upgrade to SingleStoreDB version 8.1 either stall or fail:

Update spec.template.spec.containers[0].image to singlestore/operator:3.40.3-d2c54262.
Delete the leaf-ag1 StatefulSet.

Warning

It is only possible to upgrade to a later SingleStoreDB engine image. The engine upgrade cannot be rolled back.

Perform an Upgrade

On this page

Upgrade the Operator

Upgrade the SingleStoreDB Engine

Was this article helpful?

On this page

Was this article helpful?