Red Hat Quay Release Notes

With this release, Clair indexer data is now included with downstream builds. This allows Red Hat Quay administrators to more easily reference indexers in the clair-config.yaml file when running Clair in an air-gapped or disconnected environment.

For more information, see Clair in disconnected environments.

With the release of Red Hat Quay 3.14, the v2 UI now renders model card information for machine learning models that include a model card. When a manifest has a certain annotation (for example, application/x-mlmodel) and a model card stored as a layer in the manifest, a Model Card tab is displayed on the tag’s information page. The information on the Model Card page provides users with comprehensive insights into each model, and can help enhance a user’s understanding of models stored within their registry.

To view model card information, Red Hat Quay users or administrators must push an artifact to a repository. The artifact must have have an accompanying model card. This information renders under Repository → <tag_name> → Model Card.

For more information, see Viewing model card information by using the v2 UI.

Previously, when configuring tag expiration for Red Hat Quay, the yearly option was unavailable on the Red Hat Quay v2 UI. With this update, users can now configure default tag expiration to occur yearly on the Red Hat Quay v2 UI. This can be set by using the Red Hat Quay UI or in your config.yaml file. For example:

DEFAULT_TAG_EXPIRATION: 1y
TAG_EXPIRATION_OPTIONS:
  - 1y

The following configuration fields have been added for the model card rendering feature on the Red Hat Quay v2 UI:

These configuration fields are enabled and set by default in your config.yaml file:

FEATURE_UI_MODELCARD: true
UI_MODELCARD_ARTIFACT_TYPE: application/x-mlmodel
UI_MODELCARD_ANNOTATION:
  org.opencontainers.image.description: "Model card metadata"
UI_MODELCARD_LAYER_ANNOTATION:
  org.opencontainers.image.title: README.md

For more information, see Viewing model card information by using the v2 UI.

The IGNORE_UNKNOWN_MEDIATYPES configuration field has been removed. By default, Red Hat Quay accepts all artifact types.

The following configuration fields have been added to the original (v1) UI. You can use these fields to customize the footer of your on-prem v1 UI.

FOOTER_LINKS:
  "TERMS_OF_SERVICE_URL": "https://www.index.hr"
  "PRIVACY_POLICY_URL": "https://www.example.hr"
  "SECURITY_URL": "https://www.example.hr"
  "ABOUT_URL": "https://www.example.hr"

When pushing an unsupported image type, for example, an AI model, to a Red Hat Quay registry, the Security Report and Packages pages on the UI fail to load. This occurs because these image types are stuck in a Querying status and, as a result, the pages of these tabs are left blank. This is a known issue and will be fixed in a future version of Red Hat Quay.

In OpenShift Container Platform clusters with multiple ingress controllers defined, the Red Hat Quay Operator iterates through the list of available ingress controllers are uses the first one that it encounters to determine the cluster hostname. However, the order of ingress controllers in this list is not guaranteed to be consistent across reconciliation cycles. Consequently, the Operator might pick a different ingress controller, leading it to detect a change in the cluster hostname and initiate a new reconciliation process. This can lead to instability in quay pods and your Red Hat Quay on OpenShift Container Platform deployment.

Use one of the following methods to avoid this issue: