Tomáš Nožička

I think a lot of it is just historical and because the same scylla container was/is used without orchestration. > When scylla fails it should be restarted by k8s liveness...

I suppose would scale the members in every rack.

It's on my list for Monday, apologies for the delay. (if you we not to get a review pls ping me on Tue)

We just use the container image that scylla produces. It likely needs an adjustment in supervisord not to restart the process and leave that to the container runtime and the...

Good catch, I wasn't looking that deep, my point was that it's out of our control. Wanna file a bug for github.com/scylladb/scylla with your findings?

good job, tracing this down. We need /readyz in scylla, pinging all ports and trying to figure out which ones should it be sucks and current API doesn't event allow...

best if we can get some traction on https://github.com/scylladb/scylla/issues/8275

Hi @GavinJE, thanks for your contribution. Can you please use just one PR to fix all the typos you see? like #847 #848 #849 #850

While going through the Kubernetes audit logs, on upgrade, one of the pods got recycled PodIP after the other cluster - maybe gossip was using it for membership an that's...

I am lowering the priority and scheduling it to 1.8. This has always been the case so it's not a regression in the operator. Unfortunately, we use the ScyllaCluster name...