clickhouse difficulty with defining custom config.xml

[luke-zhu]

Name and Version

bitnami/clickhouse 9.4.4

What steps will reproduce the bug?

I run the following command:

helm template test ./charts/bitnami/clickhouse --values data-2026-04/clickhouse-values.yaml

I receive the following error:

Error: YAML parse error on clickhouse/templates/configmap.yaml: error converting YAML to JSON: yaml: line 17: did not find expected comment or line break

Here is a copy-pastable command:

helm template test ./charts/bitnami/clickhouse --values <(cat <<EOF
commonAnnotations: 
  testkey: "testvalue"
configuration:
  testkey: "testvalue"
EOF
) > clickhouse-output.yaml

Error: YAML parse error on clickhouse/templates/configmap.yaml: error converting YAML to JSON: yaml: line 17: did not find expected comment or line break

Use --debug flag to render out invalid YAML

Are you using any custom parameters or values?

commonAnnotations: 
  testkey: "testvalue"

configuration:
  testkey: "testvalue"

# These also don't work
#
# configuration: {"a": "b"}
# configuration: | 
#   <yandex>
#     <testkey></testvalue>
#   </yandex>

What is the expected behavior?

I hope to be able to define the config.xml using the configuration parameter.

Preferably I hope to copy-paste XML instead of potentially having to translate everything into a YAML dictionary before being able to debug futher.

What do you see instead?

Error: YAML parse error on clickhouse/templates/configmap.yaml: error converting YAML to JSON: yaml: line 17: did not find expected comment or line break

Additional information

Hello,

I am a Master's student.

Given the usefulness of this repository, I may use it significantly over the next couple of years.

I have found ~10 small-changes possible so far. These would conventionally be considered bugs or improvements. I have manually vetted and believe 80% are worth the changes they would require.

The academic area I focus on rewards finding many bugs, while VMWare appears to reward other indicators.
I hope to get a better idea of what type of reports (or fixes) would best work for your team. It appears that perhaps it is best for me to provide bug reports with copy-pastable commands as suggested by the Pull Request template.

It is unfortunate that these differences may make it hard to collaborate.
This reminds me of an old saying: "大学之道，在明明德", which I would anachronistic translate into "College's path lies in the Ming Dynasty's morality." I hope to continue collaborating in a pro-social manner, keeping in mind all people (relatives/亲 and new/新) as the 德 character suggests.

English is my native language but I am happy to communicate in others to practice.