From f5df2b2251a3af650f7f1fc7e68b44fdcd499937 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Tue, 22 Jul 2025 14:05:18 -0500 Subject: [PATCH 1/2] warn against force delete --- .../kubernetes/re-clusters/delete-custom-resources.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/content/operate/kubernetes/re-clusters/delete-custom-resources.md b/content/operate/kubernetes/re-clusters/delete-custom-resources.md index 6ec48ffd3d..77c6f89f27 100644 --- a/content/operate/kubernetes/re-clusters/delete-custom-resources.md +++ b/content/operate/kubernetes/re-clusters/delete-custom-resources.md @@ -11,6 +11,17 @@ linkTitle: Delete custom resources weight: 70 --- +{{< warning >}} +Use graceful deletion methods + +When deleting Redis Enterprise resources or pods, try to avoid use `kubectl delete --force` or similar force deletion commands, as these can lead to: +- Data loss or corruption +- Incomplete cleanup of resources +- Cluster instability + +If resources appear stuck during deletion, investigate the underlying cause rather than forcing deletion. See [Troubleshoot Redis Enterprise pods]({{< relref "/operate/kubernetes/recommendations/troubleshoot-pods" >}}) for guidance. +{{< /warning >}} + ## Multi-namespace management Before you can delete a namespace, you must remove the Redis custom resources ([REDB](#delete-a-database-redb), [REC](#delete-a-redis-enterprise-cluster-rec), and [operator](#delete-operator-from-one-namespace)) residing within a namespace before you can delete that namespace. Deleting namespace containing an REDB may cause errors or data loss. From 04eeba64b18c6b7608216af38a584e4ba042e95d Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com> Date: Thu, 24 Jul 2025 10:36:29 -0500 Subject: [PATCH 2/2] Update content/operate/kubernetes/re-clusters/delete-custom-resources.md Co-authored-by: David Dougherty --- .../operate/kubernetes/re-clusters/delete-custom-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/kubernetes/re-clusters/delete-custom-resources.md b/content/operate/kubernetes/re-clusters/delete-custom-resources.md index 77c6f89f27..7ce7decd3f 100644 --- a/content/operate/kubernetes/re-clusters/delete-custom-resources.md +++ b/content/operate/kubernetes/re-clusters/delete-custom-resources.md @@ -14,7 +14,7 @@ weight: 70 {{< warning >}} Use graceful deletion methods -When deleting Redis Enterprise resources or pods, try to avoid use `kubectl delete --force` or similar force deletion commands, as these can lead to: +When deleting Redis Enterprise resources or pods, try to avoid using `kubectl delete --force` or similar force deletion commands, as these can lead to: - Data loss or corruption - Incomplete cleanup of resources - Cluster instability