Currently, there is no LimitRange configured for the projects on the CentOS CI Infra OCP4 clusters. This results in containers being able to use unbounded resources by default.

An excerpt from the k8s documentation at https://kubernetes.io/docs/concepts/policy/limit-range/:

By default, containers run with unbounded compute resources on a Kubernetes cluster. [...] A LimitRange provides constraints that set default request/limit for compute resources.

While it is possible to explicitly set the requests/limits for each container separately, it makes a lot of sense to have sensible defaults (or at least more sensible than unbounded) for when this is not the case.

This is related to https://pagure.io/centos-infra/issue/8. It will make it easier for projects to stay within the quota.

As an example, this is default LimitRange for the cki project in ocp.prod.psi.redhat.com:

apiVersion: v1
kind: LimitRange
metadata:
  name: cki-limits
spec:
  limits:
    - default:
        cpu: 500m
        memory: 1000Mi
      defaultRequest:
        cpu: 300m
        memory: 400Mi
      type: Container