Michael Burman
Michael Burman
## Bug Report **Describe the bug** When updating the cass-operator from 1.7.1 to 1.8.0, the user needs to run the following command: ```console kubectl patch crd cassandradatacenters.cassandra.datastax.com -p '{"spec":{"preserveUnknownFields":false}}' ```...
**What this PR does**: Automates the CRD upgrader's step of setting preserveUnknownFields to false when updating to newest k8ssandra version (cass-operator 1.8.0). This is required, otherwise the CRD upgrade will...
**What this PR does**: Creates a new option that does rolling restart outside cads-operator's controller. **Which issue(s) this PR fixes**: Fixes #385 **Checklist** - [x] Changes manually tested - [x]...
**What is missing?** At the moment, to do a rolling restart, we must modify the CassandraDatacenter spec. We want a task that would do the same without requiring the modification...
**What happened?** I manually edited the StatefulSet annotations to cause rolling restart (same way as kubectl rollout restart would do). First pod was started correctly again and got to 2/2...
**What is missing?** At the moment, it is possible for us to start replacing more nodes than the cluster can in reality handle. This is because we continue with the...
**What happened?** The master has no VMware specific PSP (PersistentServicesPlatform) features enabled. The features are still in the code, but the controller does not listen for those events and the...
**What is missing?** If we have issues in the running pod which are visible from the Cassandra logs, we could create events directly from the SystemLogger which we deploy as...
**What happened?** Cassandra 4.x removed the support for Thrift interface. However, we still open a port for it when deploying a Cassandra 4.x deployment: ```yaml - containerPort: 9160 name: thrift...
**What is missing?** Currently management-api is considered to be always in the port 8080 by the cass-operator. We should allow PodHost to define a port as well to simplify testing...