Perform an Upgrade
On this page
Upgrades include either upgrading the Operator, or upgrading the SingleStoreDB YAML configuration files.
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.
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.
with a later version of Operator image.template. spec. containers[0]. 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.
kubectl apply -f sdb-operator.yaml
Upgrade the SingleStoreDB Engine
Note
To upgrade to SingleStoreDB version 8.
Please confirm that the cluster is stable before performing the upgrade.
-
Edit the sdb-cluster.
yaml file and replace spec.
andnodeImage. repository spec.
with a later version of the node image.nodeImage. tag -
Apply the upgrade.
kubectl apply -f sdb-cluster.yaml
Should an upgrade to SingleStoreDB version 8.
-
Update
spec.
totemplate. spec. containers[0]. image singlestore/operator:3.
.40. 3-d2c54262 -
Delete the
leaf-ag1
StatefulSet.
Warning
It is only possible to upgrade to a later SingleStoreDB engine image.
Last modified: July 24, 2023