# Configure storage

## Storage defaults

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. Note that 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. The example values.yaml files provided in the [GitHub Helm chart repo](https://github.com/StackVista/helm-charts/tree/master/stable/stackstate/installation/examples) show how you can customize the `size` of volumes. The `storageClass` can be added in a similar fashion.

In the example below, all services that store data are switched to rely on the storageClass named `standard` and not use the default storageClass configured for the cluster:

{% tabs %}
{% tab title="values.yaml" %}

```yaml
elasticsearch:
  volumeClaimTemplate:
    storageClassName: "standard"
      resources:
        requests:
            # size of volume for each Elasticsearch pod
            storage: 250Gi

hbase:
  hdfs:
    datanode:
      persistence:
        storageClass: "standard"
        # size of volume for HDFS data nodes
        size: 250Gi

    namenode:
      persistence:
        storageClass: "standard"
        # size of volume for HDFS name nodes
        size: 20Gi


kafka:
  persistence:
    storageClass: "standard"
    # size of persistent volume for each Kafka pod
    size: 50Gi


zookeeper:
  persistence:
    storageClass: "standard"
    # size of persistent volume for each Zookeeper pod
    size: 50Gi
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://archivedocs.stackstate.com/5.1/setup/install-stackstate/kubernetes_openshift/storage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.