[Bitnami/cassandra] How to custom individual configure in cassandra.yaml

[conceptjs]

Name and Version

bitnami/cassandra 9.2.3

What is the problem this feature will solve?

Currently Bitnami/cassandra helm chart uses existingConfiguration to use a configMap to customize the configurations:

existingConfiguration: cassandra-config

However, existingConfiguration expects the whole cassandra.yaml to be used for customization. In our case we only want to customize a single property or a few properties in cassandra.yaml file without overwrite the entire cassandra.yaml file.

The discussion in issue #5574 suggested that we can copy cassandra.yaml from the default configure in the pod, customize the attribute(s) and use it as configMap in existingConfiguration.

However, this approach won't work in a cluster deployment where multiple pods are created and they have different cassandra.yaml with its own ip address configure.

What is the feature you are proposing to solve the problem?

Bitnami/cassandra helm chart should support individual properties with existingConfiguration, where we can pass only single or a few properties, for example:

batch_size_fail_threshold_in_kb: 10000

During the deployment only this property will be overwritten by the configMap and all other properties in cassandra.yaml file should be kept with default values.

Any comment or suggestion on alternative solutions or am I missing something here? Help is much appreciated!

What alternatives have you considered?

No response

[carrodher]

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.

[github-actions]

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.

[github-actions]

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.

[akshayvermadtu]

Any update on this ?

I am not able to override the Cassandra config yaml in case of HA k8s deployment of Bitnami cassandra.

[seleznev]

As a workaround, individual options can be overridden via extraEnvVars chart value with CASSANDRA_CFG_YAML_* environment variables (see for details: bitnami/containers#63358).

For example:

extraEnvVars:
- name: CASSANDRA_CFG_YAML_MEMTABLE_ALLOCATION_TYPE
  value: offheap_objects
- name: CASSANDRA_CFG_YAML_MEMTABLE_OFFHEAP_SPACE
  value: 2GiB

[akshayvermadtu]

What if I want to pass unique value to each Cassandra replica ?

For example in case of restoring from snapshot, I need to pass different initial_token value to each Cassandra replica.

[jalsanishant]

I got with this same issue passing value of cassandra.yaml through custom existingconfiguration, configmap or something else? opened similar issue-
#32184