This Kubernetes operator automates the Cassandra operations such as deploying a new rack aware cluster, adding/removing nodes, configuring the C* and JVM parameters, upgrading JVM and C* versions, and many more...
We triggered a rolling restart with the casskop plugin:
kubectl casskop restart --crd cassandra-bgl --full
We applied the initial configuration of the cluster
kubectl apply -f cassandra-bgl.yaml
What did you expect to see?
Nothing is supposed to happen as we applied the initial yaml.
We are not supposed to have an error
What did you see instead? Under which circumstances?
We got the message:
The cassandraclusters "cassandra-bgl" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update
Bug Report
What did you do?
What did you expect to see? Nothing is supposed to happen as we applied the initial yaml. We are not supposed to have an error
What did you see instead? Under which circumstances? We got the message: The cassandraclusters "cassandra-bgl" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update
Environment
casskop version: 0.5.4
Kubernetes version information: 1.16.8
Kubernetes cluster kind: Orange internal cluster
Cassandra version: 3.11
Possible Solution Similar problem on other operator: https://github.com/argoproj/argo-cd/issues/3657#issuecomment-634933960
Seems not to come from the operator but likely the plugin