# Quickstart

### Pre-requisites

In order to setup redis-operator, you'll need access to a Kubernetes cluster:-

* [Virtualbox](https://www.virtualbox.org/wiki/Downloads) - hypervisor to run a Kubernetes cluster
* [Minikube](https://kubernetes.io/docs/setup/minikube/) - for Kubernetes cluster creation on local machine
* [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) - to interact with Kubernetes cluster

### Deploying Redis Operator(Minikube)

#### Start a local minikube cluster

Minikube is a minimal Kubernetes cluster run in a virtual machine (here in VirtualBox).

```bash
minikube start --vm-driver virtualbox
```

From now on your local Kubernetes client `kubectl` is configured to use your just started Minikube cluster.

#### Create a new namespace

First, we need to create a namespace for our resources to be deployed in. This is for the sake of separation and keeping order:

```bash
kubectl create namespace redis-operator
```

Redis operator by default watches for every change in Redis Configuration.

### Standalone Redis Setup

```bash
kubectl apply -f example/redis-standalone-example.yaml -n redis-operator
```

### Cluster Redis Setup

```bash
kubectl apply -f example/redis-cluster-example.yaml -n redis-operator
```

### Cleanup

```bash
# To delete standalone setup
kubectl delete -f example/redis-standalone-example.yaml -n redis-operator
# To delete cluster setups
kubectl delete -f example/redis-cluster-example.yaml -n redis-operator
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opstreelabs.in/redis-operator/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.