Dapr can use any Redis instance - containerized, running on your local dev machine, or a managed cloud service. If you already have a Redis store, move on to the Configuration section.
We can use Helm to quickly create a Redis instance in our Kubernetes cluster. This approach requires Installing Helm.
-
Install Redis into your cluster. Note that we're explicitly setting an image tag to get a version greater than 5, which is what Dapr' pub/sub functionality requires. If you're intending on using Redis as just a state store (and not for pub/sub), you do not have to set the image version.
helm repo add bitnami https://charts.bitnami.com/bitnami helm install redis bitnami/redis
-
Run
kubectl get pods
to see the Redis containers now running in your cluster. -
Add
redis-master:6379
as theredisHost
in your redis.yaml file. For example:metadata: - name: redisHost value: redis-master:6379
-
Next, we'll get our Redis password, which is slightly different depending on the OS we're using:
-
Windows: Run
kubectl get secret --namespace default redis -o jsonpath="{.data.redis-password}" > encoded.b64
, which will create a file with your encoded password. Next, runcertutil -decode encoded.b64 password.txt
, which will put your redis password in a text file calledpassword.txt
. Copy the password and delete the two files. -
Linux/MacOS: Run
kubectl get secret --namespace default redis -o jsonpath="{.data.redis-password}" | base64 --decode
and copy the outputted password.
Add this password as the
redisPassword
value in your redis.yaml file. For example:metadata: - name: redisPassword value: lhDOkwTlp0
-
Note: this approach requires having an Azure Subscription.
- Open this link to start the Azure Cache for Redis creation flow. Log in if necessary.
- Fill out necessary information and check the "Unblock port 6379" box, which will allow us to persist state without SSL.
- Click "Create" to kickoff deployment of your Redis instance.
- Once your instance is created, you'll need to grab the Host name (FQDN) and your access key.
- for the Host name navigate to the resources "Overview" and copy "Host name"
- for your access key navigate to "Access Keys" under "Settings" and copy your key.
- Finally, we need to add our key and our host to a
redis.yaml
file that Dapr can apply to our cluster. If you're running a sample, you'll add the host and key to the providedredis.yaml
. If you're creating a project from the ground up, you'll create aredis.yaml
file as specified in Configuration. Set theredisHost
key to[HOST NAME FROM PREVIOUS STEP]:6379
and theredisPassword
key to the key you copied in step 4. Note: In a production-grade application, follow secret management instructions to securely manage your secrets.
NOTE: Dapr pub/sub uses Redis Streams that was introduced by Redis 5.0, which isn't currently available on Azure Managed Redis Cache. Consequently, you can use Azure Managed Redis Cache only for state persistence.
To setup Redis, you need to create a component for state.redis
.
The following yaml file demonstrates how to define each.
TLS: If the Redis instance supports TLS with public certificates it can be configured to enable or disable TLS true
or false
.
Failover: When set to true
enables the failover feature. The redisHost should be the sentinel host address. See Redis Sentinel Documentation
Note: yaml files below illustrate secret management in plain text. In a production-grade application, follow secret management instructions to securely manage your secrets.
Create a file called redis.yaml, and paste the following:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.redis
metadata:
- name: redisHost
value: <HOST>
- name: redisPassword
value: <PASSWORD>
- name: enableTLS
value: <bool> # Optional. Allowed: true, false.
- name: failover
value: <bool> # Optional. Allowed: true, false.
kubectl apply -f redis.yaml
To run locally, create a components
dir containing the YAML file and provide the path to the dapr run
command with the flag --components-path
.