From 5eec3bca828b3e65a744968fa5018f358c4ff477 Mon Sep 17 00:00:00 2001 From: Ayush Pateria Date: Fri, 2 Feb 2018 21:24:14 +0530 Subject: [PATCH] Update persistent-volumes.md (#7155) * Add deprecation warning to recycle reclaim policy. * Format the deprecation warning --- docs/concepts/storage/persistent-volumes.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/concepts/storage/persistent-volumes.md b/docs/concepts/storage/persistent-volumes.md index 31b606725e..9091f39277 100644 --- a/docs/concepts/storage/persistent-volumes.md +++ b/docs/concepts/storage/persistent-volumes.md @@ -108,6 +108,9 @@ The Retain reclaim policy allows for manual reclamation of the resource. When th #### Recycling +**Warning:** The recycling reclaim policy is being deprecated. Instead, the recommended approach is to use dynamic provisioning. +{: .warning} + If supported by appropriate volume plugin, recycling performs a basic scrub (`rm -rf /thevolume/*`) on the volume and makes it available again for a new claim. However, an administrator can configure a custom recycler pod template using the Kubernetes controller manager command line arguments as described [here](/docs/admin/kube-controller-manager/). The custom recycler pod template must contain a `volumes` specification, as shown in the example below: