Reference

Resources to help you manage Redis Enterprise custom resources on Kubernetes.

Redis Enterprise for Kubernetes

This reference documentation covers Redis Enterprise custom resources, API specifications, and practical instructions for creating, configuring, and managing Redis Enterprise deployments on Kubernetes.

Work with custom resources

Redis Enterprise for Kubernetes uses custom resources to manage clusters and databases. Use standard Kubernetes tools to create, modify, and delete these resources.

Create custom resources

Use kubectl apply with YAML manifests to create custom resources:

kubectl apply -f my-redis-cluster.yaml
kubectl apply -f my-redis-database.yaml

View custom resources

Use these commands to list and inspect existing custom resources:

# List Redis Enterprise clusters
kubectl get rec

# List Redis Enterprise databases
kubectl get redb

# List Active-Active databases
kubectl get reaadb

# List remote clusters
kubectl get rerc

# Get detailed information about a specific resource
kubectl describe rec my-cluster
kubectl describe redb my-database

Modify custom resources

Edit the YAML manifest and reapply to update custom resources:

# Edit and apply updated manifest
kubectl apply -f updated-redis-cluster.yaml

# Or edit directly (not recommended for production)
kubectl edit rec my-cluster
kubectl edit redb my-database

YAML examples

Find complete YAML examples for common deployment scenarios:

  • YAML examples - Ready-to-use YAML configurations for different deployment types

Example categories

  • Basic deployment - Essential YAML files for simple Redis Enterprise deployment
  • Rack awareness - YAML examples for rack-aware deployments across availability zones
  • Active-Active - YAML examples for Active-Active databases across multiple clusters
  • Multi-namespace - YAML examples for deploying across multiple namespaces

API reference

Review complete API specifications for all Redis Enterprise custom resources:

Core resources

Active-Active resources

Compatibility

Check supported Kubernetes distributions and versions:

Best practices

Follow these best practices when working with custom resources:

  • Use version control: Store your YAML manifests in version control systems
  • Validate before applying: Use kubectl apply --dry-run=client to validate changes
  • Monitor resource status: Check resource status after you apply changes
  • Follow naming conventions: Use consistent naming for easier management
  • Document configurations: Add annotations and labels to describe resource purpose
RATE THIS PAGE
Back to top ↑