questdb Helm Chart (v1.0.0) Fails to Render - Duplicate storageClassName Key When persistence.storageClass Is Set

Products

• Bitnami Premium (Bitnami Secure Images)

Issue/Introduction

When deploying the Bitnami Secure Images questdb Helm chart (version 1.0.0) with the persistence.storageClass value set, helm template or helm install fails with a YAML parsing error instead of successfully rendering the StatefulSet manifest.

Example command and error:

helm template x oci://<registry>/charts/debian-12/questdb --version 1.0.0 --set persistence.storageClass=myclass --debug

Error: YAML parse error on questdb/templates/statefulset.yaml: error converting YAML to JSON: yaml: line 180: mapping values are not allowed in this context

Environment

Product: Bitnami Secure Images
Chart: questdb
Chart Version: 1.0.0

Cause

The chart's templates/statefulset.yaml (around line 180) hardcodes a literal storageClassName: key immediately before invoking the shared common.storage.class helper template from the bitnami/common library chart:

storageClassName: {{ include "common.storage.class" (dict "persistence" .Values.persistence "global" .Values.global) }}

The common.storage.class helper already renders the complete key-value pair (e.g. storageClassName: myclass), not just the value. Because the questdb template also prepends its own storageClassName: literal, the rendered output contains the key twice on a single line:

storageClassName: storageClassName: myclass

This is invalid YAML (two mapping keys on one line), which causes the parse failure. 

Resolution

This issue is fixed in Version 1.1.0. Please upgrade to this version to address this issue.