Tomáš Nožička

Step one would be a PoC to validate the approach and start adding the label to scylla images. We then have to wait for the old image to become unsupported...

@rzetelskik can you link the PoC you did? I don't thing we've written a proposal but (for the record) the next step would be to get a label into scylla...

The case of a kubernetes node being decommissioned is covered by `AutomaticOrphanedNodeCleanup` although there is a race if the scylla node wouldn't be bootstrapped yet which would get stuck on...

also there is a similar issue for non-namespaced sysctls https://github.com/scylladb/scylla-operator/issues/868

note that the default failure threshold is 3 (need to fix that) so you need to double check the events if readiness started failing

also this one looks similar https://github.com/scylladb/scylla-operator/runs/4522166605?check_suite_focus=true#step:12:668 [e2e-artifacts.tar.lz4.zip](https://github.com/scylladb/scylla-operator/files/7717067/e2e-artifacts.tar.lz4.28.zip) ``` STEP: Waiting for namespace "e2e-test-scyllacluster-v7crr-bc2dk" to be removed. 12/14/21 15:42:19.796

+1

it's there now

in CI / e2e sysctls are tuned for the nodes, I think that's where we should direct this in general but the automatic node sysctl tuning didn't land yet.

I wonder whether such cluster passes the Kubernetes conformance tests. Looking at a random webhook test, say https://github.com/kubernetes/kubernetes/blob/4e0069b9097ea19bb5af642893175dd092e64920/test/e2e/apimachinery/webhook.go#L403-L410 and the definition for the deployment https://github.com/kubernetes/kubernetes/blob/4e0069b9097ea19bb5af642893175dd092e64920/test/e2e/apimachinery/webhook.go#L832-L836 would suggest it fails. If...