Tomáš Nožička

This is just cosmetic for the single namespace deployment, as @seandilda investigated there is no fix to allow emitting those events, without privilege escalation. It doesn't affect route handling, just...

Removing the old `caCertificate` seems reasonable. Could you try to remove it manually and can confirm that fixes the issue? (I can follow up with a PR if that's confirmed.)

/reopen /remove-lifecycle rotten /lifecycle frozen /kind bug

@FaisalDefry any chance you run openshift-acme for a while with staging an then switched to prod? if that's the case there is a secret (named `acme-account`) that has a key...

> But for the “default” project and some other project who didnt get the request after i change the anotation, do you have any clue? Which annotation? the one on...

Well, with passthrough generating certificates doesn't make sense but I am not sure if the controller should change it for you or report proper error. I'll keep it here as...

/reopen /remove-lifecycle rotten /lifecycle frozen /kind feature

If you look at the audit logs, can you dump the PV to see why the provissioner thinks differently? https://github.com/kubernetes/minikube/blob/f567893cdbb8e98a0348c1d93455af71cf6ce12c/pkg/storage/storage_provisioner.go#L97-L112

seems like the provisioner uses random UUID that by definition won't work with a restart https://github.com/kubernetes/minikube/blob/f567893cdbb8e98a0348c1d93455af71cf6ce12c/pkg/storage/storage_provisioner.go#L52 looking at the logs, what was the cause a a very first restart of...

to sum it up here, this is waiting for the new scylla local storage provisioner https://github.com/scylladb/scylla-operator/pull/979#issuecomment-1145676235