Closed st3v closed 1 month ago
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/neo4j 0.1.8
What architecture are you using?
None
What steps will reproduce the bug?
Run
helm template foo oci://registry-1.docker.io/bitnamicharts/neo4j --set-json persistence.annotations='{"bar": "baz"}' --set 'service.type=ClusterIP'
and look at the annotations on thevolumeClaimTemplate
of theStatefulSet
resource.Are you using any custom parameters or values?
--set-json persistence.annotations='{"bar": "baz"}' --set 'service.type=ClusterIP'
What is the expected behavior?
What do you see instead?
Additional information
If I "wrap" the annotations in another object things work...
Other charts do not require this extra "wrapper object". For example, the following works just fine:
Cassandra:
helm template foo oci://registry-1.docker.io/bitnamicharts/cassandra --set-json persistence.annotations='{"bar": "baz"}'
Postgresql:
helm template foo oci://registry-1.docker.io/bitnamicharts/postgresql --set-json primary.persistence.annotations='{"bar": "baz"}'
MySQL:
helm template foo oci://registry-1.docker.io/bitnamicharts/mysql --set-json primary.persistence.annotations='{"bar": "baz"}'
I'm not certain but believe the problem might be due to the extra
fromYaml
at the end of this line.