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.