The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
# ClusterResourceOverride Admission Webhook for OpenShift ## Introduction Scheduling is based on resources requested, while quota and hard limits refer to resource limits, which can be set higher than requested resources. The difference between request and limit determines the level of overcommit; for instance, if a container is given a memory request of 1Gi and a memory limit of 2Gi, it is scheduled based on the 1Gi request being available on the node, but could use up to 2Gi; so it is 200% overcommitted. If OpenShift Container Platform administrators would like to control the level of overcommit and manage container density on nodes, ClusterResourceOverride Admission Webhook can be configured to override the ratio between request and limit set on developer containers. In conjunction with a per-project LimitRange specifying limits and defaults, this adjusts the container limit and request to achieve the desired level of overcommit.
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | ClusterResourceOverride |
| Summary | Empty |
| Description | Manages level of overcommit of Pod Resource(s) |
| Provider | Red Hat |
| Product component | Cluster Resource Override Admission Operator |
| Maintainer | Red Hat, Inc. |
| License | GPLv2+ |
| Source location | https://github.com/openshift/cluster-resource-override-admission |
| Repository name | openshift/ose-clusterresourceoverride-rhel9 |
| Image version | v4.18.0 |
| Architecture | amd64 |
| Commit location | https://github.com/openshift/cluster-resource-override-admission/commit/513e458c3381b4216520748a92549cf4740b7ce3 |
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Use the following command(s) from a system with podman installed.
Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.
Use skopeo to copy the source image to a local directory
Inspect the image
Untar the contents
Begin examining and using the content.