From fd9a10c5eaeeb5cdd256eda637bb8f9d375afe77 Mon Sep 17 00:00:00 2001 From: Ricardo Niepel Date: Mon, 4 Nov 2019 10:06:41 -0500 Subject: [PATCH] Remove explicit Redis Helm version (#228) --- concepts/components/redis.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/concepts/components/redis.md b/concepts/components/redis.md index 1470938a7..96ed41085 100644 --- a/concepts/components/redis.md +++ b/concepts/components/redis.md @@ -13,7 +13,8 @@ Dapr can use any Redis instance - containerized, running on your local dev machi 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). -1. Install Redis into your cluster: `helm install stable/redis --name redis --set image.tag=5.0.5-debian-9-r104`. 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. +1. Install Redis into your cluster: `helm install stable/redis --name redis`. +> Note that you need a Redis 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), also a lower version can be used. 2. Run `kubectl get pods` to see the Redis containers now running in your cluster. 3. Add `redis-master:6379` as the `redisHost` in your [redis.yaml](#configuration) file. For example: ```yaml