The Persistent Volume Claim (PVC) persists even after scaling in the Logstash deployment

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

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.