{
  "schema_version": 2,
  "id": "operate/kubernetes/reference/yaml/multi-namespace",
  "title": "Multi-namespace examples",
  "url": "https://redis.io/docs/latest/operate/kubernetes/reference/yaml/multi-namespace/",
  "summary": "YAML examples for deploying Redis Enterprise across multiple Kubernetes namespaces.",
  "tags": [
    "docs",
    "operate",
    "kubernetes"
  ],
  "last_updated": "2026-09-28T15:03:12+01:00",
  "page_type": "content",
  "content_hash": "211d33208e922d14e228d603c9fd31c2512b5b575f4bebcbc40f3d9399762cd4",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "Multi-namespace deployment lets a single Redis Enterprise operator manage clusters and databases in different namespaces, providing better resource isolation and organization.\n\nMulti-namespace deployment enables:\n- Namespace isolation: Separate Redis Enterprise resources by team, environment, or application\n- Centralized management: Single operator manages multiple namespaces\n- Resource sharing: Efficient use of cluster resources across namespaces\n- Flexible RBAC: Fine-grained permissions per namespace\n\nThis example shows:\n- Operator namespace: `redis-enterprise-operator` (where the operator and REC run)\n- Consumer namespaces: `app-production`, `app-staging` (where REDB resources are created)\n\nFor complete deployment instructions, see [Manage databases in multiple namespaces](https://redis.io/docs/latest/operate/kubernetes/re-clusters/multi-namespace)."
    },
    {
      "id": "operator-service-account",
      "title": "Operator service account",
      "role": "content",
      "text": "Deploy these resources in the namespace where the Redis Enterprise operator runs."
    },
    {
      "id": "operator-cluster-role",
      "title": "Operator cluster role",
      "role": "content",
      "text": "Grant the operator cluster-wide permissions to manage resources across namespaces."
    },
    {
      "id": "operator-cluster-role-binding",
      "title": "Operator cluster role binding",
      "role": "content",
      "text": ""
    },
    {
      "id": "consumer-role",
      "title": "Consumer role",
      "role": "content",
      "text": ""
    },
    {
      "id": "consumer-role-binding",
      "title": "Consumer role binding",
      "role": "content",
      "text": "Consumer namespace configuration:\n\n- `subjects.name`: Must match the operator service account name\n- `subjects.namespace`: Must be the operator namespace, not the consumer namespace\n- `roleRef.name`: Must match the consumer role name"
    },
    {
      "id": "next-steps",
      "title": "Next steps",
      "role": "content",
      "text": "- [Configure networking across namespaces](https://redis.io/docs/latest/operate/kubernetes/networking)\n- [Set up monitoring for multi-namespace deployment](https://redis.io/docs/latest/operate/kubernetes/re-clusters/connect-prometheus-operator)\n- [Learn about resource management](https://redis.io/docs/latest/operate/kubernetes/recommendations)"
    },
    {
      "id": "related-documentation",
      "title": "Related documentation",
      "role": "related",
      "text": "- [Manage databases in multiple namespaces](https://redis.io/docs/latest/operate/kubernetes/re-clusters/multi-namespace)\n- [RBAC configuration](https://redis.io/docs/latest/operate/kubernetes/security)\n- [Kubernetes namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)"
    }
  ],
  "examples": []
}