StackState doesn't specify a specific storage class on its PVC's (persistent volume claims) by default, for cloud providers like EKS and AKS this means the default storage class will be used.
The defaults for those storage classes are typically to delete the PV (persistent volume) when the PVC is deleted. However, even when running helm delete to remove a stackstate release the PVC's will remain present within the namespace and will be reused if a helm install is run in the same namespace with the same release name.
To remove the PVC's either remove them manually with kubectl delete pvc or delete the entire namespace.
Customize storage
You can customize the storageClass and size settings for different volumes in the Helm chart. These example values files show how to change the storage class or the volume size. These can be merged to change both at the same time.
global:# The storage class for most of the persistent volumesstorageClass:"standard"elasticsearch:volumeClaimTemplate:storageClassName:"standard"victoria-metrics-0:server:persistentVolume:storageClass:"standard"victoria-metrics-1:server:persistentVolume:storageClass:"standard"
elasticsearch:volumeClaimTemplate:resources:requests:# size of volume for each Elasticsearch podstorage:250Gihbase:hdfs:datanode:persistence:# size of volume for HDFS data nodessize:250Ginamenode:persistence:# size of volume for HDFS name nodessize:20Gikafka:persistence:# size of persistent volume for each Kafka podsize:50Gizookeeper:persistence:# size of persistent volume for each Zookeeper podsize:50Givictoria-metrics-0:server:persistentVolume:size:250Givictoria-metrics-1:server:persistentVolume:size:250Gistackstate:components:checks:tmpToPVC:volumeSize:2GihealthSync:tmpToPVC:volumeSize:2Gistate:tmpToPVC:volumeSize:2Gisync:tmpToPVC:volumeSize:2Givmagent:persistence:size:10Gi