content/operate/kubernetes/7.22/reference/yaml/multi-namespace.md
Multi-namespace deployment lets a single Redis Enterprise operator manage clusters and databases in different namespaces, providing better resource isolation and organization.
Multi-namespace deployment enables:
This example shows:
redis-enterprise-operator (where the operator and REC run)app-production, app-staging (where REDB resources are created)For complete deployment instructions, see [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/7.22/re-clusters/multi-namespace" >}}).
Deploy these resources in the namespace where the Redis Enterprise operator runs.
{{<embed-yaml "k8s/service_account.md" "operator-service-account.yaml">}}
Grant the operator cluster-wide permissions to manage resources across namespaces.
{{<embed-yaml "k8s/multi-ns_operator_cluster_role.md" "operator-cluster-role.yaml">}}
{{<embed-yaml "k8s/multi-ns_operator_cluster_role_binding.md" "operator-cluster-role-binding.yaml">}}
{{<embed-yaml "k8s/multi-ns_role.md" "consumer-role.yaml">}}
{{<embed-yaml "k8s/multi-ns_role_binding.md" "consumer-role-binding.yaml">}}
Consumer namespace configuration:
subjects.name: Must match the operator service account namesubjects.namespace: Must be the operator namespace, not the consumer namespaceroleRef.name: Must match the consumer role name