Tutorial: Configure state store and pub/sub message broker

You can use Helm to create a Redis instance in our Kubernetes cluster. Before beginning, install Helm v3.

Install Redis into your cluster:

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm install redis bitnami/redis --set image.tag=6.2

For Dapr’s Pub/sub functionality, you’ll need at least Redis version 5. For state store, you can use a lower version. Note that adding --set architecture=standalone to the install command creates a single replica Redis setup, which can save memory and resources if you are working in a local environment.

Run kubectl get pods to see the Redis containers now running in your cluster:

$ kubectl get pods
NAME             READY   STATUS    RESTARTS   AGE
redis-master-0   1/1     Running   0          69s
redis-replicas-0    1/1     Running   0          69s
redis-replicas-1    1/1     Running   0          22s

For Kubernetes:

• The hostname is redis-master.default.svc.cluster.local:6379
• The secret, redis, is created automatically.

Verify you have an Azure subscription.

1. Open and log into the Azure portal to start the Azure Redis Cache creation flow.
2. Fill out the necessary information.
   • Dapr Pub/sub uses Redis streams introduced by Redis 5.0. To use Azure Redis Cache for Pub/sub, set the version to (PREVIEW) 6.
3. Click Create to kickoff deployment of your Redis instance.
4. Make note of the Redis instance hostname from the Overview page in Azure portal for later.
   • It should look like xxxxxx.redis.cache.windows.net:6380.
5. Once your instance is created, grab your access key:

   1. Navigate to Access Keys under Settings.

   2. Create a Kubernetes secret to store your Redis password:

      kubectl create secret generic redis --from-literal=redis-password=*********
      

1. Deploy a Redis instance from AWS Redis.

2. Note the Redis hostname in the AWS portal for later.

3. Create a Kubernetes secret to store your Redis password:

   kubectl create secret generic redis --from-literal=redis-password=*********
   

1. Deploy a MemoryStore instance from GCP Cloud MemoryStore.

2. Note the Redis hostname in the GCP portal for later.

3. Create a Kubernetes secret to store your Redis password:

   kubectl create secret generic redis --from-literal=redis-password=*********
   

Since Kubernetes files are applied with kubectl, they can be created in any directory.

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore
  namespace: default
spec:
  type: state.redis
  version: v1
  metadata:
  - name: redisHost
    value: <REPLACE WITH HOSTNAME FROM ABOVE - for Redis on Kubernetes it is redis-master.default.svc.cluster.local:6379>
  - name: redisPassword
    secretKeyRef:
      name: redis
      key: redis-password
  # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache)
  # - name: enableTLS
  #   value: true 

Note the above code example uses the Kubernetes secret you created earlier when setting up a cluster.

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
  namespace: default
spec:
  type: pubsub.redis
  version: v1
  metadata:
  - name: redisHost
    value: <REPLACE WITH HOSTNAME FROM ABOVE - for Redis on Kubernetes it is redis-master.default.svc.cluster.local:6379>
  - name: redisPassword
    secretKeyRef:
      name: redis
      key: redis-password
 # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache)
  # - name: enableTLS
  #   value: true 

Note the above code example uses the Kubernetes secret you created earlier when setting up a cluster.

Run kubectl apply -f <FILENAME> for both state and pubsub files:

kubectl apply -f redis-state.yaml
kubectl apply -f redis-pubsub.yaml