Modify Redis Cluster guide doc

kubedb · Feb 20, 2019 · ec625f0 · ec625f0
1 parent 42f858d
commit ec625f0
Showing 1 changed file with 2 additions and 11 deletions.
diff --git 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).