Description of problem:

OCP conformance test "[sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel]" fails on Red Hat OpenShift on IBM Cloud. The pods causing the failure are owned my IBM and should be granted an exception. I suspect other cloud providers may need similar exceptions. As a result, it may be best to ignore limits for managed cluster pods in the kube-system namespace.

Version-Release number of selected component (if applicable):
4.8.2

How reproducible:
Always.

Steps to Reproduce:
1. Run OCP conformance test on a ROKS version 4.8.2 cluster.

Actual results:

fail [github.com/onsi/ginkgo@v4.7.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Aug 2 16:51:01.635: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
apps/v1/DaemonSet/kube-system/ibmcloud-block-storage-driver/container/ibmcloud-block-storage-driver-container defines a limit on cpu of 300m which is not allowed (rule: "apps/v1/DaemonSet/kube-system/ibmcloud-block-storage-driver/container/ibmcloud-block-storage-driver-container/limit[cpu]")
apps/v1/DaemonSet/kube-system/ibmcloud-block-storage-driver/container/ibmcloud-block-storage-driver-container defines a limit on memory of 300Mi which is not allowed (rule: "apps/v1/DaemonSet/kube-system/ibmcloud-block-storage-driver/container/ibmcloud-block-storage-driver-container/limit[memory]")
apps/v1/Deployment/kube-system/ibm-file-plugin/container/ibm-file-plugin-container defines a limit on cpu of 200m which is not allowed (rule: "apps/v1/Deployment/kube-system/ibm-file-plugin/container/ibm-file-plugin-container/limit[cpu]")
apps/v1/Deployment/kube-system/ibm-file-plugin/container/ibm-file-plugin-container defines a limit on memory of 200Mi which is not allowed (rule: "apps/v1/Deployment/kube-system/ibm-file-plugin/container/ibm-file-plugin-container/limit[memory]")
apps/v1/Deployment/kube-system/ibm-storage-watcher/container/ibm-storage-watcher-container defines a limit on cpu of 200m which is not allowed (rule: "apps/v1/Deployment/kube-system/ibm-storage-watcher/container/ibm-storage-watcher-container/limit[cpu]")
apps/v1/Deployment/kube-system/ibm-storage-watcher/container/ibm-storage-watcher-container defines a limit on memory of 200Mi which is not allowed (rule: "apps/v1/Deployment/kube-system/ibm-storage-watcher/container/ibm-storage-watcher-container/limit[memory]")
apps/v1/Deployment/kube-system/ibmcloud-block-storage-plugin/container/ibmcloud-block-storage-plugin-container defines a limit on cpu of 300m which is not allowed (rule: "apps/v1/Deployment/kube-system/ibmcloud-block-storage-plugin/container/ibmcloud-block-storage-plugin-container/limit[cpu]")
apps/v1/Deployment/kube-system/ibmcloud-block-storage-plugin/container/ibmcloud-block-storage-plugin-container defines a limit on memory of 300Mi which is not allowed (rule: "apps/v1/Deployment/kube-system/ibmcloud-block-storage-plugin/container/ibmcloud-block-storage-plugin-container/limit[memory]")
v1/Pod/kube-system/ibm-master-proxy-static-<node>/container/ibm-master-proxy-static defines a limit on cpu of 300m which is not allowed (rule: "v1/Pod/kube-system/ibm-master-proxy-static-<node>/container/ibm-master-proxy-static/limit[cpu]")
v1/Pod/kube-system/ibm-master-proxy-static-<node>/container/ibm-master-proxy-static defines a limit on memory of 512M which is not allowed (rule: "v1/Pod/kube-system/ibm-master-proxy-static-<node>/container/ibm-master-proxy-static/limit[memory]")

Expected results:

Pass

Additional info:

ROKS version 4.8.2 is in development at the moment and not publicly available.