删除自定义资源

本文介绍如何从 Kubernetes 环境中删除 Redis Enterprise 集群和 Redis Enterprise 数据库。

适用于 Kubernetes 的 Redis Enterprise

多命名空间管理

在删除命名空间之前，必须先删除驻留在命名空间中的 Redis 自定义资源（REDB、REC 和 operator），然后才能删除该命名空间。删除包含 REDB 的命名空间可能会导致错误或数据丢失。

删除数据库 （REDB）

要删除由 Redis Enterprise Kubernetes作员管理的数据库，请运行kubectl delete redb <your-db-name>从 K8s 集群。

当您删除数据库时，您的数据和 REDB 自定义资源也会被删除。

删除 Redis Enterprise 集群 （REC）

要删除由 Operator 管理的 Redis Enterprise 集群，请执行以下作：

  1. 删除集群中的所有数据库。

  2. 跑kubectl delete rec <your-rec-name>从 K8s 集群。

当您删除集群时，您的数据库和 REC 自定义资源也会被删除。但是，在此过程中不会删除集群的持久性卷声明 （PVC）。如果要删除 PVC，则必须手动删除它们。

删除运算符

有两种方法可以删除运算符。您可以删除整个 Operator 捆绑包，但这也会删除 Operator 创建的任何集群范围的资源。要仅删除特定命名空间中的资源并保持其他集群范围的资源不变，您需要手动删除每个资源。

无论您是决定删除整个捆绑包还是仅从特定命名空间中删除资源，都必须删除运算符 ConfigMap（operator-environment-config).

kubectl delete cm operator-environment-config

Delete operator bundle

To delete the operator from your K8s cluster, you can delete the operator bundle with:

  • kubectl delete -f bundle.yaml for non-OpenShift K8s deployments
  • kubectl delete -f openshift.bundle.yaml for OpenShift deployments

This will remove the operator and its custom resource definitions (CRDs) from your K8s cluster.

Warning:
The Redis Enterprise CRDs are non-namespaced resources, meaning they are shared across your entire K8s cluster. Deleting CRDs in one namespace will delete custom resources in every other namespace across the K8s cluster.

Delete operator from one namespace

If you have Redis Enterprise clusters running in different namespaces on the same K8s cluster, deleting the entire operator bundle might cause data loss.

To safely delete the operator from one namespace without affecting the others, delete the operator files individually, excluding the CRD files:

kubectl delete -f role.yaml
kubectl delete -f role_binding.yaml
kubectl delete -f service_account.yaml
kubectl delete -f admission-service.yaml
kubectl delete -f operator.yaml

You will also need to remove the namespaceSelector section from the validating webhook.

Delete an Active-Active database (REAADB)

  1. On one of the existing participating clusters, delete the REEADB (substituting <reaadb-name> with your database name).
kubectl delete reaadb <reaadb-name>
  1. Verify the REAADB no longer exists.
kubectl get reaadb -o=jsonpath='{range .items[*]}{.metadata.name}'

Delete a remote cluster (RERC)

  1. Verify the RERC you want to delete isn't listed as a participating cluster in any REAADB resources.

    If an RERC is still listed as a participating cluster in any database, the deletion will be blocked.

  2. On one of the existing participating clusters, delete the RERC (substituting <rerc-name> with your database name).

kubectl delete rerc <rerc-name>
  1. Verify the RERC no longer exists.
kubectl get rerc -o=jsonpath='{range .items[*]}{.metadata.name}'

Troubleshoot REDB deletion

The operator attaches a finalizer to the Redis Enterprise database (REDB) object. This makes sure the database is deleted before the REDB custom resource is removed from the K8s cluster.

If the operator isn't running, or some other fatal error occurs, the finalizer isn't removed automatically by the operator. In this case, you won't be able to delete your REDB resource.

If this happens, you can remove the finalizer manually.

Warning:
If you remove the finalizer manually, there is no guarantee that the underlying REDB has been deleted. This may cause resource issues and require manual intervention.
kubectl patch redb <your-db-name> --type=json -p \
    '[{"op":"remove","path":"/metadata/finalizers","value":"finalizer.redisenterprisedatabases.app.redislabs.com"}]'

Troubleshoot REC deletion

The operator attaches a finalizer to the Redis Enterprise cluster (REC) object. This makes sure the Redis cluster is deleted before the REC custom resource is removed from the K8s cluster.

If the operator isn't running, or some other fatal error occurs, the finalizer isn't removed automatically by the operator. In this case, you won't be able to delete your REC resource.

If this happens, you can remove the finalizer manually.

Warning:
If you remove the finalizer manually, there is no guarantee that the underlying REC has been deleted. This may cause resource issues and require manual intervention.
kubectl patch rec <your-rec-name> --type=json -p \
    '[{"op":"remove","path":"/metadata/finalizers","value":"redbfinalizer.redisenterpriseclusters.app.redislabs.com"}]'
RATE THIS PAGE
Back to top ↑