Hi,
I’m trying to understand how to persist Prometheus data. I installed using helm installer of prometheus-operator on microk8s. The default is that it just uses emptyDir and I’m still struggling to understand how to configure it to use a glusterfs volume.
Please let me know if this is not the right place to talk about prometheus installation via helm.
Installing via helm produces a configuration that works just fine, apart from the above mention persistence issue. Nevertheless I cannot really understand the manifest that is created: I can’t see where the StatefulSet is created (so I’m not able to look at the chart to guess how to add my volume):
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/prometheus-prometheus-node-exporter 1 1 1 1 1 <none> 14m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/postgresql-exporter 1/1 1 1 3d22h
deployment.apps/prometheus-kube-prometheus-operator 1/1 1 1 14m
deployment.apps/prometheus-kube-state-metrics 1/1 1 1 14m
deployment.apps/prometheus-grafana 1/1 1 1 14m
NAME DESIRED CURRENT READY AGE
replicaset.apps/postgresql-exporter-7f58bf9fbb 1 1 1 3d22h
replicaset.apps/prometheus-kube-prometheus-operator-599b7945f9 1 1 1 14m
replicaset.apps/prometheus-kube-state-metrics-548959f4fc 1 1 1 14m
replicaset.apps/prometheus-grafana-67f66d645c 1 1 1 14m
NAME READY AGE
statefulset.apps/alertmanager-prometheus-kube-prometheus-alertmanager 1/1 14m
statefulset.apps/prometheus-prometheus-kube-prometheus-prometheus 1/1 14m
but if I do helm get manifest -n prometheus prometheus I don’t see any definition of StatefulSet…
Any hint understanding this manifest is appreciated