Michael Burman

I don't think that ticket you linked is the reason, as this test works fine 4.30.6. I'm not even sure if we've used the older version ever in these tests....

Here's the manual output also: ```console ➜ k8ssandra-operator git:(main) /usr/local/bin/yq ea '.spec.cassandra.datacenters.[] as $item ireduce (0; . +1)' test/testdata/fixtures/multi-dc/k8ssandra.yaml test/testdata/fixtures/single-dc/k8ssandra.yaml 3 ➜ k8ssandra-operator git:(main) yq --version yq (https://github.com/mikefarah/yq/) version v4.30.6...

Actions to take here: * Instead of checking CassandraDatacenter's status of the HTTPS, we need to check if ObservedGeneration < Generation of CassandraDatacenter and if the target Pod has HTTPS...

| @burmanm is this ticket still current? It is from last year so I'm confirming before I start work on it. Yes, it is. | Also, can you clarify what...

Actually, what it is missing is the clusterName prefix which is present in every other object. Otherwise the naming uses the same methods as other resources.

Now, while fixing when creating a new one is easy, this will require us to also delete the old one. Will have to use the new field metadataVersion.

cert-manager simply mounts the crt files to the disk (through secret), that's perfectly normal. It seems you have some issues in your Kubernetes environment as even the operator can't reliably...

None of those logs have any indication that it would have even noticed your CassandraDatacenter. That's all startup logs of the operator, not the actual processing instructions. So the operator...

That log: ``2024-10-21T09:49:14.536Z ERROR controller-runtime.source.EventHandler `` is from the operator, not from the Cassandra pod.

Closing this due to inactivity.