编辑主动-主动数据库的参与集群

使用 Redis Enterprise for Kubernetes 将参与集群添加或删除到现有主动-主动数据库的步骤。

适用于 Kubernetes 的 Redis Enterprise
注意：
此功能在 6.4.2-6 及更高版本中正式发布受支持。其中一些功能在 6.4.2-4 和 6.4.2-5 中作为预览版提供。请升级到 6.4.2-6 以获取完整的正式发布功能和错误修复。以及后来。

添加参与集群

使用以下步骤将参与的集群添加到适用于 Kubernetes 的现有 Redis Enterprise Active-Active Database （REAADB）。

先决条件

要准备 Redis Enterprise 集群 （REC） 以参与主动-主动数据库，请执行准备参与集群中的以下任务：

  • 确保集群满足硬件和命名要求。
  • 启用 Active-Active 控制器。
  • 配置外部路由。
  • 配置ValidatingWebhookConfiguration.

收集 REC 凭证

要与其他集群通信，所有参与的集群都需要访问所有其他集群的管理员凭证。

  1. 获取新参与集群的 REC 凭证密钥。

    kubectl get secret -o yaml <rec-name>

    This example shows an admin credentials secret for an REC named rec-boston:

    apiVersion: v1
data:
  password: ABcdef12345
  username: GHij56789
kind: Secret
metadata:
  name: rec-boston
type: Opaque

  2. Create a secret for the new participating cluster named redis-enterprise-<rerc> and add the username and password.

    The example below shows a secret file for a remote cluster named rerc-logan .

    apiVersion: v1
data:
  password: ABcdef12345
  username: GHij56789
kind: Secret
metadata:
  name: redis-enterprise-rerc-logan
type: Opaque

  3. Apply the file of collected secrets to every participating REC.

    kubectl apply -f <rec-secret-file>

If the admin credentials for any of the clusters change, update and reapply the file to all clusters.

Create RERC

  1. From one of the existing participating clusters, create a RedisEnterpriseRemoteCluster (RERC) custom resource for the new participating cluster.

    This example shows an RERC custom resource for an REC named rec-boston in the namespace ns-massachusetts.

    apiVersion: app.redislabs.com/v1alpha1
kind: RedisEnterpriseRemoteCluster
metadata:
  name: rerc-logan
spec:
  recName: rec-boston
  recNamespace: ns-massachusetts
  apiFqdnUrl: test-example-api-rec-boston-ns-massachusetts.example.com
  dbFqdnSuffix: -example-cluster-rec-boston-ns-massachusetts.example.com
  secretName: redis-enterprise-rerc-logan

  2. Create the RERC custom resource.

    kubectl create -f <new-RERC-file>

  3. Check the status of the newly created RERC custom resource.

    kubectl get rerc <RERC-name>

    The output should look like this:

    NAME        STATUS   SPEC STATUS   LOCAL
rerc-logan   Active   Valid         true

Edit REAADB spec

  1. Patch the REAADB spec to add the new RERC name to the participatingClusters, replacing <reaadb-name> and <rerc-name> with your own values.

    kubectl patch reaadb <reaadb-name> < --type merge --patch '{"spec": {"participatingClusters": [{"name": "<rerc-name>"}]}}'

  2. View the REAADB participatingClusters status to verify the cluster was added.

    kubectl get reaadb <reaadb-name> -o=jsonpath='{.status.participatingClusters}'

    The output should look like this:

    [{"id":1,"name":"rerc-ohare"},{"id":2,"name":"rerc-reagan"},{"id":3,"name":"rerc-logan"}]

Remove a participating cluster

  1. On an existing participating cluster,remove the desired cluster from the participatingCluster section of the REAADB spec.

    kubectl edit reaadb <reaadb-name>

  2. On each of the other participating clusters, verify the status is active and the spec status is Valid and the cluster was removed.

    kubectl get reaadb <reaadb-name -o=jasonpath=`{.status}`

    The output should look like this:

    {... ,"participatingClusters":[{"id":1,"name":"rerc1"},{"id":2,"name":"rerc2"}],"redisEnterpriseCluster":"rec1","specStatus":"Valid","status":"active"}

  3. On the removed participating cluster, list all REAADB resources on the cluster to verify they were deleted.

    kubectl get reaadb -o+jasonpath=`{range.items[*]}{.metadata.name}`
RATE THIS PAGE
Back to top ↑