John Sanda

My first attempt at fixing this was: ``` additional-jvm-opts: {{- if .Values.cassandra.auth.enabled }} - "-Dcassandra.system_distributed_replication_dc_names={{ $datacenter.name }}" {{- if .Release.IsInstall }} - "-Dcassandra.system_distributed_replication_per_dc={{ min 5 $datacenter.size }}" {{- end }}...

@jdonenine We should get this prioritized and included in the next release. It fell off my radar, but it definitely should be fixed.

>as it would decouple the number of replicas from the size of the cluster I don't understand this. Are you referring to the size of the Cassandra cluster or of...

Hi @stela-leon Can you please provide the following info: * The k8ssandra chart version you installed * Any file you specified with `helm install -f` * Any properties you set...

There have been a lot of changes since 0.17.1. Here are the latest available chart versions: ``` $ helm search repo k8ssandra NAME CHART VERSION APP VERSION DESCRIPTION k8ssandra/k8ssandra 0.52.0...

> I have the same issue after a fresh install with the latest 1.4.1. It seems the `cassandra-reaper-jmx` secret is being updated at some point after the reaper pods have...

>Some repairs are working, but when the nodes get bounced it looks like it tries to connect to wrong IPs which don't exists anymore. Hey @mikekuzak. Have you changed superuser...

@mikekuzak Am I understanding correctly that restarting the C* pod and it coming up with a different IP address causes your problem? Are you seeing this with earlier versions of...

cass-operator does not allow the superuser secret reference to be updated to point to a different secret. We should allow the secret reference to change in order to better support...

Based on what you reported the cass-operator webhook, `cass-operator-validating-webhook-configuration`, is not deployed. That makes sense given the original error you hit. How did you install k8ssandra-operator? I am curious how...