Tomáš Nožička

https://github.com/scylladb/scylla-operator/actions/runs/3220293020/jobs/5266866588#step:3:1595

could we just always use `::` to listen to both stacks?

> The operator needs to run with anyuid privileges because it wants to bind to port 443. We shouldn't listen on 443, the service should handle the redirection and we...

I think the root privs are for tuning devices and setting sysctl which are done on scylla startup

> Running the command gives below output :- the label selector seems wrong - it should be `"app.kubernetes.io/name=scylla"`, not `"app.kubernetes.io/name=scylla-incident-mgmt"` Some actionable info would be say `oc get events --sort-by=.metadata.creationTimestamp`...

flaked on master as well https://github.com/scylladb/scylla-operator/actions/runs/3064280032/jobs/4947265598#step:12:954

flaking a lot, next one https://github.com/scylladb/scylla-operator/actions/runs/3067025626/jobs/4952910620#step:12:700

I also saw a lot of these on the TLS PR

flaking a lot, last one in https://github.com/scylladb/scylla-operator/actions/runs/3086220438/jobs/4990391763#step:12:261 https://github.com/scylladb/scylla-operator/suites/8367743162/artifacts/369018669

fyi, major upgrades also flake, haven't looked whether that's related