The current k8ssandra-operator Argo CD application is configured with Replace=true in the sync options to avoid issues related to large CRDs. It's expected that this would cause removal and recreation of Cassandra resources when parent CRDs are deleted and recreating during upgrade.
Should test this to confirm that this is an issue, and if so come up with an alternate installation/configuration method that avoids this upgrade issue.
The current k8ssandra-operator Argo CD application is configured with Replace=true in the sync options to avoid issues related to large CRDs. It's expected that this would cause removal and recreation of Cassandra resources when parent CRDs are deleted and recreating during upgrade.
Should test this to confirm that this is an issue, and if so come up with an alternate installation/configuration method that avoids this upgrade issue.