1. Proposed title of this feature request
>>> Set limit quotas for kube-rbac-proxy in knative-serving resource

2. What is the nature and description of the request?
>>> The container should have a limit set, to prevent excessive resource utilization.
Customer even tried to set limits for the container in the knative-serving resource in the deployments but this did not work on the kube-rbac-proxy as it reverts to original state.

$ oc get deployment controller -o yaml
----<snip>----
image: registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:ef2c41fb899228a64cf2f61d7606a980a5f8fcae820da246d25c4f17faa0da3d
imagePullPolicy: IfNotPresent
name: kube-rbac-proxy
resources:
requests:
cpu: 10m
memory: 20Mi
securityContext:
allowPrivilegeEscalation: false
----<snip>----

3. Why does the customer need this? (List the business requirements here)
>>> Customer need limits because in their environment they have a limitrange object which requires set limits for every container.

4. List any affected packages or components.
>>> Red Hat OpenShift Serverless - The customer wants it in knative-serving namespace for kube-rbac-proxy container.