@RunLLM Helm install does not set storageClassName for vmsingle-pulsar-victoria-metrics-k8s-stack PVCs I'm deploying the Apache Pulsar Helm chart and want to use the local-path StorageClass for all persistent volumes, including those created by the VictoriaMetrics stack (vmsingle-pulsar-victoria-metrics-k8s-stack). I run:

helm install pulsar apache/pulsar --timeout 10m --set storageClassName=local-path

However, the PVCs for vmsingle-pulsar-victoria-metrics-k8s-stack are created without a storageClassName, so dynamic provisioning does not work and the pods remain pending. • The local-path StorageClass exists and works for other charts. • Setting --set storageClassName=local-path works for Pulsar core components, but not for VictoriaMetrics. • I can't find the correct value path to set the storage class for VictoriaMetrics in the Pulsar Helm chart. How can I set the storageClassName for the VictoriaMetrics PVCs when deploying Pulsar with Helm? Is there a specific value or path I need to use in the Helm command or values.yaml? Any help or working example would be greatly appreciated!

It seems likely that the Pulsar Helm chart does not directly expose a value like

storageClassName

for the VictoriaMetrics stack PVCs, since VictoriaMetrics is typically managed by a separate subchart or external chart. The correct value path for setting the storage class for VictoriaMetrics PVCs is not documented in the main Pulsar Helm chart sources, and there is no explicit mention of a value such as

victoriaMetrics.storageClassName

or similar in the available documentation. This means that setting

--set storageClassName=local-path

only affects Pulsar core components, not VictoriaMetrics PVCs, as you observed. My understanding is that you will need to consult the values schema for the VictoriaMetrics Helm chart (often used as a subchart or via kube-prometheus-stack) to find the correct path—commonly something like

vmsingle.persistentVolume.storageClassName

or

vmsingle.persistentVolumeClaim.storageClassName

. You would then pass this value using

--set vmsingle.persistentVolume.storageClassName=local-path

(or the correct path for your chart version) in your Helm install command. This is not explicitly documented in the Pulsar Helm chart docs, so you may need to check the VictoriaMetrics chart documentation or values.yaml for the exact key. Would you like more detail or a step-by-step example for a typical VictoriaMetrics Helm chart? Sources: - https://docs.streamnative.io/private/sn-upgrade-1.11.0#local-storage - https://docs.streamnative.io/private/storage-1.11.0#%3AR12pn6%3A-gradient Note: I wasn’t able to find highly relevant data sources, but above are a few potentially relevant links. 👍 1 button 👎 0 button 💡 Hint: Mention @RunLLM in the thread for followups.