Michael Burman
Michael Burman
Hi, Two different things here. The operation of "rename Datacenter" is not something Cassandra supports, so what you essentially did was to delete the existing DC and create a new...
What you see is two separate events happening here. First is the actual upgrade of cass-operator, which caused it to read the new config files and apply the cr-prefix. This...
We don't manually start/restart any pod, so the behavior you see has to come from the Kubernetes' StatefulSet controller. The only other option would be that the Node 3 lost...
Not a bad idea at all. That would however increase our minimum supported version for cass-operator from 1.23 to 1.25 (unless it's available in the CRD from 1.22 onwards when...
The data is preserved in PVs, not PVCs. k8ssandra-operator does not delete the PVs, that's controlled by your StorageClass.
Sorry for the delayed answer, but from looking at the logs, it seems it's actually a Kubernetes issue that's causing the problem. The events you posted ``Warning FailedToUpdateEndpoint`` are coming...
Can you output the MedusaBackup object you have?
Closing this, since after creating this ticket the behavior of replace has changed. The new way to do it is through CassandraTask: https://github.com/k8ssandra/cass-operator/blob/master/tests/testdata/tasks/replace_node_task.yaml That removes the PVCs and does all...
Closing stale tickets (reopen if this ever becomes interesting again).
After https://github.com/k8ssandra/cass-operator/issues/583 is done, this ticket can be closed as then all the spec modifiers are deprecated.