Description of problem:

Compliance rule ocp4-resource-requests-limits-in-deployment failing for rhacs-operatro-controller-manager operator. This rule ideally checking the resources are set or not for every container.
Operator container two container : manager and kube-rbac-proxy
ideally we don't have resources set for kube-rbac-proxy this container in other default openshift-operator. Even if try to set the resources in operator for this container it wont reflect for container. Kube-rbac-proxy container running as side car container to proceed to secured connection with application pod.

Is it possible to bypass this rule for kube-rbac-proxy container ?

~~~
oc get deployment.apps -all-namespaces -o json | jq '[ .items[] | select(.metadata.namespace | startswith("kube") or startswith("openshift-") | not) | select( .spec.template.spec.containers[].resources.requests.cpu == null or .spec.template.spec.containers[].resources.requests.memory == null or .spec.template.spec.containers[].resources.limits.cpu == null or .spec.template.spec.containers[].resources.limits.memory == null ) | .metadata.name ]'
[
"rhacs-operator-controller-manager",
"rhacs-operator-controller-manager",
"rhacs-operator-controller-manager",
"rhacs-operator-controller-manager"
~~~