Michael Burman

This also means that Stargate will not survive restore with stopped parameter (for example, schema restore).

I don't think that error is actually the snapshot one. It seems to be related to your Cassandra not being available when the readiness call was made after liveness. The...

That documentation is wrong. You can use ``Spec.Cassandra.ClusterName`` to define the real clustername and keep metadata.name as something that's valid for Kubernetes (such as rgs).

You can already set this value under podTemplateSpec/spec/priorityClassName. For example: ```yaml apiVersion: cassandra.datastax.com/v1beta1 kind: CassandraDatacenter metadata: name: dc2 spec: clusterName: cluster2 serverType: cassandra serverVersion: "4.0.7" managementApiAuth: insecure: {} size: 1...

I can transfer this ticket then, this project is not using K8ssandraCluster, but CassandraDatacenter.

The problem is Cassandra 3.11.9, which is a broken version and for that reason we don't build new images for it and are not supporting it in k8ssandra-operator. Update to...

Are there some additional tools or stuff installed to the cluster? I'm not able to even replicate the naming of the Secret objects: ``` ➜ cass-operator git:(master) ✗ kubectl get...

I don't think this provides user anything interesting. What on earth would users do with thread profiling of Cassandra? It doesn't reveal much of useful information even, given how Cassandra...

@Miles-Garnsey This is the original ticket.

@adejanovski So, here's a short description of the problem. We currently ship with only kustomize 4.x support in k8ssandra-operator, however if users want to use kubectl to install k8ssandra-operator they...