John Sanda

Thanks for the clarification. The operator could certainly handle this scenario. If it is common for k8s nodes to be removed would network storage be better/easier?

Thanks for opening this @arianvp :) Unfortunately there are other properties in spec that the are modified: * rollingRestartRequested * stopped Might be better to have a separate ticket for...

Please [add your planning poker estimate](https://app.zenhub.com/workspaces/K8ssandra-Grooming-623b197f1fcd4800110540ef/issues/k8ssandra/cass-operator/102?planning-poker) with ZenHub @burmanm

This might be easier/less messy to do in k8ssandra-operator since we have introduced a structured config approach.

I think this is an excellent idea. Note that the [design](https://discord.com/channels/836217371453685760/862058029028737034/988792078836330516) being proposed for https://github.com/k8ssandra/k8ssandra-operator/issues/556 will impact this.

We can revert to the old behavior since k8ssandra-operator is managing the endpoints for the additional-seeds-service.

Please [add your planning poker estimate](https://app.zenhub.com/workspaces/K8ssandra-Grooming-623b197f1fcd4800110540ef/issues/k8ssandra/cass-operator/347?planning-poker) with ZenHub @burmanm

There shouldnt be any new work for changes to cassandra.yaml.

Hi @zhimsun What version of cass-operator are you using? >The pods are running normally if I change the containers.securityContext.readOnlyRootFilesystem: false Did you make this change for all containers? If not,...

I tested against my local kind cluster with a slightly modified manifest. Here is mine: ```yaml # Sized to work on 3 k8s workers nodes with 1 core / 4...