Edit Redis Enterprise remote clusters

Before a RedisEnterpriseCluster (REC) can participate in an Active-Active database, it needs an accompanying RedisEnterpriseRemoteCluster (RERC) custom resource. The RERC contains details allowing the REC to link to the RedisEnterpriseActiveActiveDatabase (REAADB). The RERC resource is listed in the REAADB resource to become a participating cluster for the Active-Active database.

For more details, see the RERC API reference.

Edit RERC

Use the kubectl patch rerc <rerc-name> --type merge --patch command to patch the local RERC custom resource with your changes. For a full list of available fields, see the RERC API reference.

The following example edits the dbFqdnSuffix field for the RERC named rerc1.

kubectl patch rerc rerc1 --type merge --patch \
'{"spec":{"dbFqdnSuffix": "-example2-cluster-rec1-ns1.redis.com"}}'

Update RERC secret

If the credentials are changed or updated for a REC participating cluster, you need to manually edit the RERC secret and apply it to all participating clusters.

1. On the local cluster, update the secret with new credentials and name it with the following convention: redis-enterprise-<rerc-name>.

   A secret for a remote cluster named rerc1 would be similar to the following:

   apiVersion: v1
   data:
     password: PHNvbWUgcGFzc3dvcmQ+
     username: PHNvbWUgdXNlcj4
   kind: Secret
   metadata:
     name: redis-enterprise-rerc1
   type: Opaque
   

2. Apply the file.

   kubectl apply -f <secret-file>
   

3. Watch the RERC to verify the status is “Active” and the spec status is “Valid.”

   kubectl get rerc <rerc-name>
   

   The output should look like this:

    NAME        STATUS   SPEC STATUS   LOCAL
     rerc1   Active   Valid         true
   

   To troubleshoot invalid configurations, view the RERC custom resource events and the Redis Enterprise operator logs.

4. Verify the status of each REAADB using that RERC is “Active” and the spec status is “Valid.”

   kubectl get reaadb <reaadb-name>
   

   The output should look like this:

     NAME             STATUS   SPEC STATUS   GLOBAL CONFIGURATIONS REDB   LINKED REDBS
   example-aadb-1   active   Valid                                      
   example-aadb-2   active   Valid                                      
   

   To troubleshoot invalid configurations, view the RERC custom resource events and the Redis Enterprise operator logs.

5. Repeat the above steps on all other participating clusters.