Chapter 1. Red Hat Quay release notes

The following features have been added with Red Hat Quay 3.15.1.

With this release, a notification drawer has been added to the Red Hat Quay v2 UI. Administrators and users can view notifications from any page in the new UI via the navigation bar by clicking the bell icon. After clicking this icon, all notifications are shown in a popup box. Notifications can be cleared by clicking the X button for respective notifications.

Previously, when pulling from a proxied repository, only the layers explicitly requested by the client were cached in the Red Hat Quay registry. This behavior stemmed from Red Hat Quay only caching layers for which it received a request to the v2 blobs endpoint. Consequently, clients with existing layers on their local machines would not re-request those layers, preventing Red Hat Quay from pulling them into the registry. This limitation led to two key issues: Clair was unable to perform complete scans of these partial images due to missing layers, and the images became un-pullable if the upstream registry went down.

With this release, Red Hat Quay now caches all layers when an image is pulled from a proxied repository. This enhancement ensures that Clair can scan all images and that images remain pullable even if the upstream registry becomes unavailable.

The SKOPEO_TIMEOUT_INTERVAL configuration field has been added. With this field, Red Hat Quay administrators can adjust the time, in seconds, that a mirroring job runs before it times out. This field is required and defaults to 300 seconds, or 5 minutes. It cannot be set lower than 300 seconds.

# ...
SKOPEO_TIMEOUT_INTERVAL: 300
# ...

# ...
SKOPEO_TIMEOUT_INTERVAL: 300
# ...

For more information, see Repository mirroring.

The FEATURE_SUPERUSER_CONFIGDUMP configuration field has been added. With this field, Red Hat Quay superusers can leverage the configDump API field to return all Flask configuration fields that are set. This can be used to show proof of compliance for various security policies, such as PCI-DSS 4.0. To use this field, superusers must be defined in the config.yaml file via the SUPER_USERS configuration field.

# ...
FEATURE_SUPERUSER_CONFIGDUMP: true
# ...

# ...
FEATURE_SUPERUSER_CONFIGDUMP: true
# ...

For more information, see Retrieving the configuration file by using the API.

A new parameter, SKOPEO_TIMEOUT_INTERVAL, has been added to the createRepoMirrorConfig endpoint. This parameter allows Red Hat Quay administrators to configure the maximum duration (in seconds) that a mirroring job is allowed to run before it times out. The default value is 300 seconds (5 minutes).

See the createRepoMirrorConfig endpoint for more information.

A new superuser API parameter, v1/superuser/config, has been added to the Red Hat Quay API. With this field, superusers can return all Flask configuration fields that are set. This can be used to show proof of compliance for various security policies, such as PCI-DSS 4.0.

For example API commands, see Red Hat Quay API superuser commands.

In Red Hat Quay 3.14, model card rendering was made available on the v2 UI for machine learning models. This feature was enabled by default via the FEATURE_UI_MODELCARD parameter.

With Red Hat Quay 3.15, this feature is now disabled by default. To view model cards on the v2 UI, you must set the FEATURE_UI_MODELCARD field to True. For example:

# ...
FEATURE_UI_MODELCARD: true
# ...

# ...
FEATURE_UI_MODELCARD: true
# ...

This change will be reverted in a future version of Red Hat Quay.

There is a known issue affecting the mirroring feature of Red Hat Quay. When the mirroring process fails, the UI shows a Mirror success report, even though it has failed. This will be fixed in a future version of Red Hat Quay.