Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

Apply Changes to a Cluster

When scaling, updating, or upgrading the cluster, edit the sdb-cluster.yaml file and run the following command.

kubectl apply -f sdb-cluster.yaml

This will cause the Operator to scale, update, or upgrade the cluster. After running this command, wait for the cluster to become stable.

Refer to the appropriate section of this reference to determine which fields in the sdb-cluster.yaml file to scale, update, or upgrade the cluster.

Some updates can be achieved by updating the Operator’s command-line arguments rather than updating the cluster directly. For example, backups can be updated either via the sdb-operator.yaml file (which will first update the Operator, and the Operator will then update the cluster) or via the sdb-cluster.yaml file (where the Operator will remain unchanged, but will still update the cluster).

To update the cluster via the Operator’s command-line arguments, edit spec.template.spec.containers[0].args in the sdb-operator.yaml  file and add, update, or delete the desired command-line arguments.

Run the following command to apply these changes.

kubectl apply -f sdb-operator.yaml

The Operator pod will be restarted. After the new Operator pod has been started, wait for the cluster to become stable.

Last modified:

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In