# The Persistent Volume Claim (PVC) persists even after scaling in the Logstash deployment **URL:** \ **Category:** Logstash\ **Created:** [December 14, 2023, 5:57am UTC](https://discuss.elastic.co/t/the-persistent-volume-claim-pvc-persists-even-after-scaling-in-the-logstash-deployment/349323 "2023-12-14T05:57:32Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vignesh\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vignesh_m/32/129982_2.png) [@Vignesh\_M](https://discuss.elastic.co/u/Vignesh_M)\ **Post date:** [December 14, 2023, 5:57am UTC](https://discuss.elastic.co/t/the-persistent-volume-claim-pvc-persists-even-after-scaling-in-the-logstash-deployment/349323/1 "2023-12-14T05:57:32Z")
Hi All, We are using the `elastic/logstash` Helm chart to deploy Logstash (StatefulSet) with persistent volume enabled in one of our Kubernetes clusters. While attempting to downscale the Logstash pod count, we observed that the Persistent Volume Claim (PVC) created during the scale-out phase remains intact even after the associated pod is terminated or deleted. We use a storage class to dynamically provision Persistent Volumes (PVs), and the reclaim policy is set to 'delete.' Hence, the expected outcome is that the PV should get deleted. Could someone assist us in understanding this issue? Logstash version: 17.7.x K8's version 1.23 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 11, 2024, 5:58am UTC](https://discuss.elastic.co/t/the-persistent-volume-claim-pvc-persists-even-after-scaling-in-the-logstash-deployment/349323/2 "2024-01-11T05:58:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.