1. Proposed title of this feature request
Compliance Operator fixes sometimes using the below steps, however again after two weeks, compliance pods run into NotReady / CrashLoopBackOff state.
~~~
Yes, scans are restarted after applying the workaround:

$ oc project ccb-itslb
$ oc delete suite --all -n ccb-itslb
$ sleep 4
$ oc get pvc -o name | grep ocp4-cis | xargs oc patch -p '{"metadata":{"finalizers":null}}'
$ oc delete job rhcos-initial
$ oc create job rhcos-initial --from=cj/rhcos-scan
Actually, I don't know exactly in which step, either on delete suite or after create job rhcos-initial.

The TLS issue occurs suddenly after a certain time..., not immediately after the workaround...
~~~
2. What is the nature and description of the request?
--> Restart and Crashloop Issue of pods even applied the above action plan need to fix it permanently

3. Why does the customer need this? (List the business requirements here)
To scan the OCP cluster

4. List any affected packages or components.