Configure storage
StackState Self-hosted v5.0.x

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 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 Kubernetes cluster:
values.yaml
1
elasticsearch:
2
volumeClaimTemplate:
3
storageClassName: "standard"
4
resources:
5
requests:
6
# size of volume for each Elasticsearch pod
7
storage: 250Gi
8
​
9
hbase:
10
hdfs:
11
datanode:
12
persistence:
13
storageClass: "standard"
14
# size of volume for HDFS data nodes
15
size: 250Gi
16
​
17
namenode:
18
persistence:
19
storageClass: "standard"
20
# size of volume for HDFS name nodes
21
size: 20Gi
22
​
23
​
24
kafka:
25
persistence:
26
storageClass: "standard"
27
# size of persistent volume for each Kafka pod
28
size: 50Gi
29
​
30
​
31
zookeeper:
32
persistence:
33
storageClass: "standard"
34
# size of persistent volume for each Zookeeper pod
35
size: 50Gi
Copied!