OpenShift Resource Management Concepts

External

• https://docs.openshift.com/container-platform/latest/dev_guide/compute_resources.html#dev-guide-compute-resources
• https://docs.openshift.com/container-platform/latest/admin_guide/quota.html

Internal

• OpenShift Concepts

Overview

OpenShift provides API-level support for establishing and enforcing resource quotas. The runtime monitors resource usage and intervenes when the quotas are reached or exceeded. Resource quotas can be set up and managed on the following type of resources: the quantity of objects that can be created per project, the amount of compute resources (requests and limits on CPU and memory) consumed by the project and individually by project entities such as pods and containers, the amount of storage consumed by project entities. Opaque integer resources can also be set and monitored.

Resource monitoring and consumption is important because it insures that no projects are using more resources that is appropriate for the cluster size. Primarily, resource constraints are set by the cluster administrators, but developers can also set request and limits on compute resources.

Organizatorium

ResourceQuota object enumerates hard resource usage limits per project.

ClusterResourceQuota object enumerates hard resource usage limits across the cluster.

After a quota is first declared on a project, the system restricts the ability to create new resources that may exceed the quota until usage statistics are calculated. If the resource creation request exceeds the quota, the server will deny the action and will return an error message.

When a resource is created, the quota usage is updated immediately. When a resource is delete, the quota usage is updated during the next full per-project statistics update.

Resource Quota Definition

Operations:

• oc get quota
• oc describe quota
• oc create

Enforcement

With cgroups?

Limits

Memory Limit

Propagates as /sys/fs/cgroup/memory/memory.limit_in_bytes in container.