Tutorial: Configure state store and pub/sub message broker

Configure state store and pub/sub message broker components for Dapr

To get up and running with the state and Pub/sub building blocks, you’ll need two components:

• A state store component for persistence and restoration.
• As pub/sub message broker component for async-style message delivery.

A full list of supported components can be found here:

• Supported state stores
• Supported pub/sub message brokers

For this tutorial, we describe how to get up and running with Redis.

Step 1: Create a Redis store

Dapr can use any Redis instance, either:

• Containerized on your local dev machine, or
• A managed cloud service.

If you already have a Redis store, move on to the configuration section.

• Self-Hosted
• Kubernetes
• Azure
• AWS
• GCP

Redis is automatically installed in self-hosted environments by the Dapr CLI as part of the initialization process. You are all set! Skip ahead to the next steps.

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.

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=*********

Step 2: Configure Dapr components

Dapr defines resources to use for building block functionality with components. These steps go through how to connect the resources you created above to Dapr for state and pub/sub.

Locate your component files

• Self-Hosted
• Kubernetes

In self-hosted mode, component files are automatically created under:

• Windows: %USERPROFILE%\.dapr\components\
• Linux/MacOS: $HOME/.dapr/components

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

Create State store component

Create a file named redis-state.yaml, and paste the following:

• Self-Hosted
• Kubernetes

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore
  namespace: default
spec:
  type: state.redis
  version: v1
  metadata:
  - name: redisHost
    value: localhost: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

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.

Other stores

If using a state store other than Redis, refer to the supported state stores for information on options to set.

Create Pub/sub message broker component

Create a file called redis-pubsub.yaml, and paste the following:

• Self-Hosted
• Kubernetes

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
  namespace: default
spec:
  type: pubsub.redis
  version: v1
  metadata:
  - name: redisHost
    value: localhost: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

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.

Other stores

If using a pub/sub message broker other than Redis, refer to the supported pub/sub message brokers for information on options to set.

Hard coded passwords (not recommended)

For development purposes only, you can skip creating Kubernetes secrets and place passwords directly into the Dapr component file:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore
  namespace: default
spec:
  type: state.redis
  version: v1
  metadata:
  - name: redisHost
    value: <HOST>
  - name: redisPassword
    value: <PASSWORD>
  # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache)
  # - name: enableTLS
  #   value: true

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
  namespace: default
spec:
  type: pubsub.redis
  version: v1
  metadata:
  - name: redisHost
    value: <HOST>
  - name: redisPassword
    value: <PASSWORD>
  # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache)
  # - name: enableTLS
  #   value: true

Step 3: Apply the configuration

• Self-Hosted
• Kubernetes

When you run dapr init, Dapr creates a default redis pubsub.yaml on your local machine. Verify by opening your components directory:

• On Windows, under %UserProfile%\.dapr\components\pubsub.yaml
• On Linux/MacOS, under ~/.dapr/components/pubsub.yaml

For new component files:

1. Create a new components directory in your app folder containing the YAML files.
2. Provide the path to the dapr run command with the flag --components-path

If you initialized Dapr in slim mode (without Docker), you need to manually create the default directory, or always specify a components directory using --components-path.

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

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

Next steps

Try out a Dapr quickstart

Last modified September 14, 2022: Upmerge to 1.9 (#2793) (a35f0dcd)