Remove Reclaim Storage (#2203)

Signed-off-by: Daniel Valdivia <18384552+dvaldivia@users.noreply.github.com>

docs/tenant-storage-deletion.md

@@ -1,10 +1,17 @@
-# When one-time storage is required
+# Tenant Storage Deletion
 
-There are times when we need to do tests, and once the tests are done, we need to clean up the storage immediately. We can do the following configuration
+Deleting a tenant's storage in Kubernetes is a sensitive and controversial issue. On one hand, some users may want to
+delete storage in CI/CD scenarios. On the other hand, if configured in production environments and forgotten, it risks
+potential data loss.
 
-```$xslt
- - name: pool-0
-   reclaimStorage: true
-```
+Kubernetes does not automatically delete Persistent Volume Claims (PVCs) when a StatefulSet is deleted, due to the risk
+involved. This decision is left to the user. The MinIO Operator adheres to this practice as well.
 
-When a tenant is deleted, the associated pvc is also deleted immediately.
+To delete a tenant's storage, you should manually delete the PVCs associated with the tenant. This can be done via
+kubectl at the same time you are deleting the tenant. For example, to delete a tenant named tenant in the namespace
+ns-1, run the following commands:
+
+```bash
+kubectl -n ns-1 delete tenant tenant
+kubectl -n ns-1 delete pvc -l v1.min.io/tenant=tenant
+```