If there is an issue with other APIs, Compliance Operator can not start. This has happened also with other operators, such as AMQ (https://issues.redhat.com/browse/ENTMQBR-8664)  and could be improved as otherwise the pod is in ContainerCreating status and you have to deal first with the apiservice respective.

Example of issue:

compliance-operator.v1.4.0
2024-02-07T08:47:10.122629878-08:00 {"level":"info","ts":"2024-02-07T16:47:10.122Z","logger":"setup","msg":"Go Version: go1.20.10"}
2024-02-07T08:47:10.122629878-08:00 {"level":"info","ts":"2024-02-07T16:47:10.122Z","logger":"setup","msg":"Go OS/Arch: linux/amd64"}
2024-02-07T08:47:10.122629878-08:00 {"level":"info","ts":"2024-02-07T16:47:10.122Z","logger":"setup","msg":"Compliance Operator Version: 1.4.0"}
2024-02-07T08:47:10.122629878-08:00 {"level":"info","ts":"2024-02-07T16:47:10.122Z","logger":"setup","msg":"Watching","namespace":"openshift-compliance"}
2024-02-07T08:47:10.126354552-08:00 {"level":"info","ts":"2024-02-07T16:47:10.126Z","logger":"setup","msg":"Registering Components."}
2024-02-07T08:47:10.228584270-08:00 {"level":"info","ts":"2024-02-07T16:47:10.222Z","logger":"metrics","msg":"Registering metric: compliance_scan_error_total"}
2024-02-07T08:47:10.228584270-08:00 {"level":"info","ts":"2024-02-07T16:47:10.222Z","logger":"metrics","msg":"Registering metric: compliance_scan_status_total"}
2024-02-07T08:47:10.228584270-08:00 {"level":"info","ts":"2024-02-07T16:47:10.222Z","logger":"metrics","msg":"Registering metric: compliance_remediation_status_total"}
2024-02-07T08:47:10.228584270-08:00 {"level":"info","ts":"2024-02-07T16:47:10.222Z","logger":"metrics","msg":"Registering metric: compliance_state"}
2024-02-07T08:47:10.228584270-08:00 {"level":"info","ts":"2024-02-07T16:47:10.222Z","logger":"setup","msg":"Deriving scheduling info from pod","Pod.Name":"compliance-operator-84b6df899b-5tjnr","Pod.Namespace":"openshift-compliance"}
2024-02-07T08:47:11.340672636-08:00 I0207 16:47:11.340622       1 request.go:697] Waited for 1.046183336s due to client-side throttling, not priority and fairness, request: GET:https://100.101.64.1:443/apis/velero.io/v1?timeout=32s
2024-02-07T08:47:21.340743825-08:00 I0207 16:47:21.340695       1 request.go:697] Waited for 6.09756981s due to client-side throttling, not priority and fairness, request: GET:https://100.101.64.1:443/apis/migration.k8s.io/v1alpha1?timeout=32s
2024-02-07T08:47:21.495187083-08:00 time="2024-02-07T16:47:21Z" level=error msg="unable to retrieve the complete list of server APIs: admission.cluster.open-cluster-management.io/v1: the server is currently unable to handle the request, admission.work.open-cluster-management.io/v1: the server is currently unable to handle the requestError creating ServiceMonitor"
~                                                                                                                  

message: back-off 5m0s restarting failed container=compliance-operator pod=compliance-operator-84b6df899b-5tjnr_openshift-compliance(bbb1ac3f-3dea-42cf-8c29-b13d7983517b)