shaojini

> Hi @shaojini, thanks for the issue. The underlying problem is expressed in the message: > > > The CustomResourceDefinition "clusterserviceversions.operators.coreos.com" is invalid: metadata.annotations: Too long: must have at most...

> > Hi @shaojini, thanks for the issue. The underlying problem is expressed in the message: > > > The CustomResourceDefinition "clusterserviceversions.operators.coreos.com" is invalid: metadata.annotations: Too long: must have at...

Hi @grokspawn . I really use the link given by you to install the OLM. Now the main problem is the "apiServices" can not be installed successfully. I try to...

Hi. It seems the new version of v.0.25.0 has fixed the problem of the"OLM fails to install packageserver with FailedDiscoveryCheck error". root@k8s-master:~# kubectl get apiservices.apiregistration.k8s.io v1.packages.operators.coreos.com NAME SERVICE AVAILABLE AGE...

``` root@k8s-master:~# kubectl -n security-profiles-operator logs spod-6579n Defaulted container "security-profiles-operator" out of: security-profiles-operator, bpf-recorder, metrics, non-root-enabler (init) I0817 12:45:07.665328 1346435 main.go:260] "msg"="Set logging verbosity to 0" I0817 12:45:07.666835 1346435 main.go:266]...

Hi, @saschagrunert . Any comment for this issue? Thanks.

Hi, @saschagrunert . I have tried uninstalled and re-installed a few time, but the problem is the same. The logs given previously is taken from one of those tries (Before...

Hi, @saschagrunert . I have re-operated the issue again for comparing the "describe pod spod-xxxx" before and after the patching. The difference is to enable "recording" in the "daemon" and...

Hi @saschagrunert . That ID in the "describe" is not the actual container id. I got the ID in this way: ``` root@k8s-worker3:~# crictl ps -a CONTAINER IMAGE CREATED STATE...

Hi, @saschagrunert. The bef-recorder container log has shown the error: "error"="connect to metrics server: connect to local GRPC server: wait on retry: timed out waiting for the condition". Is it...