Redis Enterprise Active-Active for Kubernetes

The preview features below are only available for the 6.4.2-4 release.

Active-Active databases give you read-and-write access to Redis Enterprise clusters (REC) in different Kubernetes clusters or namespaces. Active-Active deployments managed by the Redis Enterprise operator require two additional custom resources: Redis Enterprise Active-Active database (REAADB) and Redis Enterprise remote cluster (RERC).

To create an Active-Active Redis Enterprise deployment for Kubernetes with these new features, first prepare participating clusters then create an Active-Active database.

For the currently supported procedure, see Create Active-Active databases for Kubernetes.

REAADB custom resource

Redis Enterprise Active-Active database (REAADB) contains a link to the RERC for each participating cluster, and provides configuration and status to the management plane.

For a full list of fields and options, see the REAADB API reference.

RERC custom resource

Redis Enterprise remote cluster (RERC) custom resource contains configuration details for all the participating clusters.

For a full list of fields and options, see the RERC API reference.

Preview limitations

  • No support for Hashicorp Vault for storing secrets (RED-95805)

  • No module support (RED-95153)

  • No support for client certificates in secrets (RED-95724)

  • No support for backup configuration (RED-95724)

  • No support for upgrading the database Redis version

  • REAADB secret status isn’t updated in source cluster (RED-96296)

    The workaround is to view the secret status in one of the remote clusters.

  • Invalid REAADB is not rejected by admission might get deleted after apply. (RED-96300)

    Fix the problems with the REAADB and reapply. Contact support if you aren’t sure why the REAADB is invalid.

  • Admission is not blocking REAADB with shardCount which exceeds license quota. (RED-96301)

    Fix the problems with the REAADB and reapply.

  • The <rec-name>/<rec-namespace> value must be unique for each RERC resource. (RED-96302)

  • Only global database options are supported, not support for specifying configuration per location.

  • No support for migration from old (manual) Active-Active database method to new Active-Active controller.