Deploy a SingleStore Cluster

Now that your various object definition files are created, you will use kubectl to do the actual object creation and cluster deployment.

Create the RBAC resources.
Shell
```
kubectl create -f  sdb-rbac.yaml
```
Create the cluster resource definition.
Shell
```
kubectl create -f sdb-cluster-crd.yaml
```
When deploying on OpenShift, the recommended deployment method, perform this step.
Shell
```
oc get namespace <the-namespace-you-want-to-deploy-in> \
-o=jsonpath='{.metadata.annotations.openshift\.io/sa\.scc\.supplemental-groups}{"\n"}'
```
This command will display output similar to 1096160000/10000. Note that the actual numbers may differ.

Copy the number before the slash (/) and replace the value in --fs-group-id (which is currently 5555) with this number in the sdb-operator.yaml file.
Deploy the Operator.
Shell
```
kubectl create -f sdb-operator.yaml
```
Verify the deployment was successful by checking the status of the pods in your Kube cluster. You should see the Operator with a status of Running.
Shell
```
kubectl get pods
```
Finally, create the cluster.
Shell
```
kubectl create -f sdb-cluster.yaml
```
After a couple minutes, run kubectl get pods again to verify the aggregator and leaf nodes all started and have a status of Running.
Shell
```
kubectl get pods
```
If you see no pods are in the Running state, then run kubectl get statefulsets to see if the statefulsets are running. If you need to debug an inoperable cluster, check the Operator logs by running kubectl logs deployment sdb-operator and then look at the various objects to see what is failing.

In this section