YAML examples on Docs

Basic deployment examples

Mon, 01 Jan 0001 00:00:00 +0000

This page provides complete YAML examples for a basic Redis Enterprise deployment on Kubernetes. These examples include all the essential components you need to deploy a Redis Enterprise cluster and create a database.

For complete deployment instructions, see Deploy on Kubernetes.

Service account

The service account provides an identity for the Redis Enterprise operator.

Rack awareness examples

Mon, 01 Jan 0001 00:00:00 +0000

This page provides YAML examples for deploying Redis Enterprise with rack awareness. Rack awareness distributes Redis Enterprise nodes and database shards across different availability zones or failure domains to improve high availability and fault tolerance.

Prerequisites

Label Kubernetes nodes with zone information
Typically uses the standard label topology.kubernetes.io/zone
Verify node labels: kubectl get nodes -o custom-columns="name:metadata.name","rack\\zone:metadata.labels.topology\.kubernetes\.io/zone"
Install the Redis Enterprise operator

For complete deployment instructions, see Deploy on Kubernetes.

Active-Active examples

Mon, 01 Jan 0001 00:00:00 +0000

This page provides YAML examples for deploying Active-Active Redis Enterprise databases across multiple Kubernetes clusters. Active-Active databases provide multi-master replication with conflict resolution, enabling global distribution and local read/write access.

For complete deployment instructions, see Active-Active databases.

Applying the configuration

To deploy Active-Active databases using these YAML files, follow Create Active-Active database (REAADB), which provides detailed instructions for preparing clusters, creating RERC resources, and deploying REAADB configurations.

Multi-namespace examples

Mon, 01 Jan 0001 00:00:00 +0000

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:

Namespace isolation: Separate Redis Enterprise resources by team, environment, or application
Centralized management: Single operator manages multiple namespaces
Resource sharing: Efficient use of cluster resources across namespaces
Flexible RBAC: Fine-grained permissions per namespace

This example shows:

Operator namespace: redis-enterprise-operator (where the operator and REC run)
Consumer namespaces: app-production, app-staging (where REDB resources are created)

For complete deployment instructions, see Manage databases in multiple namespaces.

Log collector RBAC examples

Mon, 01 Jan 0001 00:00:00 +0000

This page provides YAML examples for configuring RBAC permissions for the Redis Enterprise log collector tool. The log collector requires different permission levels depending on the collection mode you choose.

For complete log collection instructions, see Collect logs.

Prerequisites

Install the Redis Enterprise operator
Appropriate permissions to create RBAC resources in target namespaces
Understanding of your deployment model (single namespace, multi-namespace, etc.)

Collection modes

The log collector has two collection modes that require different RBAC permissions: