Michael Burman

Alright, time for some larger workaround then. I think we can do this without changing anything right now. I first had a complex scenario that I described to John using...

We might need that. I think cass-config-builder fetches cassandra 3.11.6 cassandra-env.sh and then applies its modifications to that one, thus wiping out the existing cassandra-env.sh https://github.com/datastax/cass-config-builder/blob/master/src/lcm/utils/oss_definitions_gen.clj#L194

client.go change + a task is fine (I'm not a fan of pod annotations, since we don't listen to those). I'm assuming this is a DSE specific feature.

We already support running multiple Cassandra pods on the same nodes. It's just affinities. What you're seeing is probably the use of hostNetworking which then takes the ports on the...

Yes, we don't support port changes at this point from the CRD. For mgmt-api configuration, it would be this ticket: https://github.com/k8ssandra/cass-operator/issues/242 In theory, the PodTemplateSpec in CassandraDatacenter allows to change...

Or make the seedprovider Kubernetes aware like I did in this PR: https://github.com/k8ssandra/management-api-for-apache-cassandra/pull/240

> The existing reaper will use the empty string when connecting to k8ssandra service, e.g. the name will be for example k8ssandra--service. This will cause the reaper to fail and...

The ``REAPER_CASS_CONTACT_POINTS`` is created by the following code: ``Value: fmt.Sprintf("[%s]", dc.GetDatacenterServiceName()),``. In this case, the bump of dependency changes the behavior of ``GetDatacenterServiceName()`` to ignore the empty DatacenterName so it...

The -contact-points service has Endpoints which are managed by the operator, there's no selector for that reason.

The logic of selecting the correct ConfigMap is done in the cass-operator, not by the Helm chart.