It is not clear how to install State Store on Different namespace

[tshaiman]

URL : https://docs.dapr.io/getting-started/tutorials/configure-state-pubsub/#step-1-create-a-redis-store

What content needs to be created or modified?

• installation steps on installing Redis from bitnami Helm chart needs to take into account the fact that users may want to install the chart on different namespace then the Dapr App will be installed into .
• the tutorial assume all runs from "Default" namespace.

Describe the solution you'd like

1. Add explanation on how installation StateStore to differernt namespace is performed
2. Explain what changes in the Secret fetch mechanism once Redis secret is not on the same Namespace as the App .
   It is mentioned something about Role and RoleBindings to different namespaces , but this is the Auth model , what about referencing
   both the Redis Service from another namespace ? will that change the way the Redis.yaml host looks like ?

Where should the new material be placed?
as a note / remark on the same page.
https://docs.dapr.io/getting-started/tutorials/configure-state-pubsub/#step-1-create-a-redis-store

[tshaiman]

any updates on this issue ?

[pdebruin]

Related dapr/quickstarts#1028

[pdebruin]

I agree that this can be clarified:

• Redis can be installed in a different namespace

helm upgrade --install redis bitnami/redis --namespace redis-system --create-namespace --wait

• The Redis installation automatically creates a Redis secret in that same custom namespace, which needs to be recreated in default namespace

kubectl get secret --namespace redis-system redis -o jsonpath="{.data.redis-password}" | base64 -d
kubectl create secret generic redis --from-literal=redis-password=<output from above>

[pdebruin]

You could even argue that this shouldn't belong in a tutorial but in operations docs like https://docs.dapr.io/operations/observability/tracing/zipkin/