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.
Running an OpenShift Update Service instance in a cluster is appealing for OpenShift clusters in restricted networks or for administrators that want to provide their own customized upgrade graph data.
The OpenShift Update Service is the on-premise release of Red Hat’s hosted update service. It performs the task of providing upgrade graph information to OpenShift clusters showing the recommended versions that can be safely updated to. This provides administrators with a seamless user experience for applying updates to OpenShift clusters in a restricted network.
Graph Builder fetches OpenShift release payload information (primary metadata) from any container registry (compatible with Docker registry V2 API) and builds a directed acyclic graph (DAG) representing valid upgrade edges. It is responsible for verifying that the graph described by the releases is acyclic and connected.
Policy Engine is in charge of altering a client's view of the graph by applying a set of filters which are defined within the particular Policy Engine instance. Both the input to and the output from Policy Engines is a graph, allowing multiple Policy Engines to be chained together. The first Policy Engine in a chain will fetch its graph from the Graph Builder and the last Policy Engine in a chain will serve the modified graph to the client.
Cluster Version Operator (CVO) (running on the OpenShift 4 cluster) is the end consumer of the release payloads. The client periodically queries the Policy Engine for updates and applies them if available.
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | OpenShift Update Service |
| Summary | CSV Bundle for the OpenShift Update Service Operator |
| Description | CSV Bundle for the OpenShift Update Service Operator |
| Provider | Red Hat |
| Maintainer | OTA-Team <aos-team-ota@redhat.com> |
| License | ASL 2.0 |
| Repository name | cincinnati/cincinnati-operator-metadata-container |
| Image version | v5.0.4 |
| Architecture | amd64 |
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.