increase request/limit memory/cpu to account for additional overhead

[acornett21]

Motivation

When testing some changes on various versions of OCP, I noticed that the manager pod was getting OOMKilled on some clusters and some versions of OCP. After looking into it more, we used to have a kube-rbac-proxy sidecar that was handling RBAC/etc, and had it's own memory configuration. When we took away the proxy, this means that the manager is now doing that lifting, but we never increased the memory or cpu.

Sidecar Config

operator-certification-operator/config/default/manager_auth_proxy_patch.yaml

Lines 24 to 29 in e98c442

	limits:
	cpu: 500m
	memory: 128Mi
	requests:
	cpu: 5m
	memory: 64Mi

Manager Config

operator-certification-operator/config/manager/manager.yaml

Lines 62 to 68 in 96b8ee4

	resources:
	limits:
	cpu: 200m
	memory: 100Mi
	requests:
	cpu: 100m
	memory: 20Mi

Changes

Increase memory/cpu to be close to the additive values of when we had two containers (proxy + manager), for the manager container.