From d5f8096030b442ba7da8627f88230ae56acfa28f Mon Sep 17 00:00:00 2001 From: Haishi2016 Date: Sun, 13 Oct 2019 22:42:49 -0700 Subject: [PATCH] redis clarification (#113) --- concepts/components/redis.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/concepts/components/redis.md b/concepts/components/redis.md index 795f09d34..13f8a69e5 100644 --- a/concepts/components/redis.md +++ b/concepts/components/redis.md @@ -20,6 +20,8 @@ Dapr can use any Redis instance - containerized, running on your local dev machi 5. Run `kubectl get svc` and copy the cluster IP of your `redis-master`. 6. 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 provided `redis.yaml`. If you're creating a project from the ground up, you'll create a `redis.yaml` file as specified in [Configuration](#configuration). Set the `redisHost` key to `[IP FROM PREVIOUS STEP]:6379` and the `redisPassword` key to the key you copied in step 4. **Note:** In a production-grade application, follow [secret management](https://github.com/dapr/docs/blob/master/concepts/components/secrets.md) instructions to securely manage your secrets. +> **NOTE:** Dapr pub-sub uses [Redis Streams](https://redis.io/topics/streams-intro) 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. + ### Creating a Redis Cache in your Kubernetes Cluster using Helm We can use [Helm](https://helm.sh/) to quickly create a Redis instance in our Kubernetes cluster. This approach requires [Installing Helm](https://github.com/helm/helm#install).