Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

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, while SingleStore 9.0 is recommended for production workloads.

Download the Operator

The singlestore/operator can be pulled from Docker Hub or from the Red Hat container registry. When pulling singlestore/operator from the Red Hat container registry, you must first authenticate with the registry using a registry service account. For more information on how to acquire the singlestore/operator container from the Red Hat container registry, follow the instructions on the Operator container page in the Red Hat Container Catalog.

Pull the image down onto a host directly to cache it locally. Alternatively, the Operator can be pulled down automatically from any container registry where the Operator is located (such as a private registry, Red Hat OpenShift, or Docker Hub) by referencing it in the sdb-operator.yaml definition file as described in the next step. An account is not required for Docker Hub.

When pulling the image, you can test deployments using the most current Operator build by specifying singlestore/operator and the desired image. For production environments, you should pin your container version with a specific tag (e.g. docker pull singlestore/operator:3.0.13-5d1a7361).

Once you have access to the singlestore/operator image, proceed with creating the object definition files for your cluster.

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