🐞 Bug report

Hi,

i have installed the securecodebox operator and a zaproxy + generic webhook on an AWS cluster and it works great.
But i have made the exact same installation procedure on an OVH cluster, everything seems ok in installation logs, CRDs are present, operator and minio pods in securecodebox-system namespace too. But when i try to launch a scan, i can see the log trace:

scan.execution.securecodebox.io/zap-baseline-scan-xxx created

and a new line in kubectl get scans but with a state staying empty and no new job created for this new scan....

Did anyone encountered this problem before ? Is there something to check somewhere in the cluster configuration ? How can i test that the controller responsible for crd creation is operational with enough access rights ?

For information i am using helm v3.3.3 on a kubernetes v1.20.2 cluster.

Thanks in advance.