From ec625f0d493f46c81cc449d4846a6ef6110902d3 Mon Sep 17 00:00:00 2001 From: shudipta Date: Wed, 20 Feb 2019 17:41:49 +0600 Subject: [PATCH] Modify Redis Cluster guide doc --- docs/guides/redis/clustering/redis-cluster.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/docs/guides/redis/clustering/redis-cluster.md b/docs/guides/redis/clustering/redis-cluster.md index 80acef6c0..266084310 100644 --- a/docs/guides/redis/clustering/redis-cluster.md +++ b/docs/guides/redis/clustering/redis-cluster.md @@ -373,9 +373,9 @@ e49d748b815db355f29e670ba62b669627384273 172.17.0.10:6379@16379 master - 0 15505 Notice that 172.17.0.8 is the new master and 172.17.0.4 is the slave of 172.17.0.8. -## Delete Redis and WipeOut DormantDatabase +## Cleaning up -You can wipe out a `Redis` while deleting the object by setting `spec.terminationPolicy` to `WipeOut`. KubeDB operator will delete any relevant resources of this `Redis` database (i.e, PVCs, Seervice, StatefulSets). +Clean what you created in this tutorial. ```yaml $ kubedb edit rd -n demo redis-cluster -o yaml @@ -396,15 +396,6 @@ $ kubedb delete rd redis-cluster -n demo redis.kubedb.com "redis-cluster" deleted ``` -If `spec.treminationPolicy` is not set to `WipeOut` while deleting the `Redis` object, then only this object, StatefulSets and Service will be deleted and `kubedb-operator` won't delete related PVCs. So, users still can access the stored data. - -In that case, just delete the `DormantDatabase`. - -```console -$ kubectl delete drmn redis-cluster -n demo -dormantdatabase "redis-cluster" deleted -``` - ## Next Steps - Monitor your Redis database with KubeDB using [out-of-the-box CoreOS Prometheus Operator](/docs/guides/redis/monitoring/using-coreos-prometheus-operator.md).