Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Red Hat Quay Release Notes

Red Hat Quay 3.15

Red Hat Quay

Red Hat OpenShift Documentation Team

Abstract

Red Hat Quay Release Notes

Preface

Red Hat Quay container registry platform provides secure storage, distribution, and governance of containers and cloud-native artifacts on any infrastructure. It is available as a standalone component or as an Operator on OpenShift Container Platform. Red Hat Quay includes the following features and benefits:

  • Granular security management
  • Fast and robust at any scale
  • High velocity CI/CD
  • Automated installation and updates
  • Enterprise authentication and team-based access control
  • OpenShift Container Platform integration

Red Hat Quay is regularly released, containing new features, bug fixes, and software updates. To upgrade Red Hat Quay for both standalone and OpenShift Container Platform deployments, see Upgrade Red Hat Quay.

Important

Red Hat Quay only supports rolling back, or downgrading, to previous z-stream versions, for example, 3.14.2 → 3.14.1. Rolling back to previous y-stream versions (3.15 → 3.14) is not supported. This is because Red Hat Quay updates might contain database schema upgrades that are applied when upgrading to a new version of Red Hat Quay. Database schema upgrades are not considered backwards compatible.

Downgrading to previous z-streams is neither recommended nor supported by either Operator based deployments or virtual machine based deployments. Downgrading should only be done in extreme circumstances. The decision to rollback your Red Hat Quay deployment must be made in conjunction with the Red Hat Quay support and development teams. For more information, contact Red Hat Quay support.

Documentation for Red Hat Quay is versioned with each release. The latest Red Hat Quay documentation is available from the Red Hat Quay Documentation page. Currently, version 3 is the latest major version.

Note

Prior to version 2.9.2, Red Hat Quay was called Quay Enterprise. Documentation for 2.9.2 and prior versions are archived on the Product Documentation for Red Hat Quay 2.9 page.

Chapter 1. RHBA-2025:8408 - Red Hat Quay 3.15.0 release

Issued 2025-07-07

Red Hat Quay release 3.15 is now available with Clair 4.8. The bug fixes that are included in the update are listed in the RHBA-2025:9240 advisory. For the most recent compatibility matrix, see Quay Enterprise 3.x Tested Integrations. For information on the release cadence of Red Hat Quay, see the Red Hat Quay Life Cycle Policy.

1.1. Red Hat Quay documentation changes

The following documentation changes have been made with the Red Hat Quay 3.15 release:

  • The Configure Red Hat Quay book has been refactored. This book now provides expanded information on the following topics:

    • Understanding the Red Hat Quay configuration file
    • On premise Red Hat Quay configuration overview
    • Red Hat Quay on OpenShift Container Platform configuration overview, including the QuayRegistry custom resource

Additionally, the configuration fields have been re-organized into associated topics. Example YAML snippets are available for each configuration option. Lastly, the configuration options link to an associated procedure when relevant.

1.2. Red Hat Quay new features and enhancements

The following updates have been made to Red Hat Quay.

1.2.1. v2 UI notification drawer

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.

Note

Currently, the v2 UI does not support the Red Hat Quay Notification option when selecting a notification method. You can select the Red Hat Quay Notification method by using the v1 UI.

1.2.2. Proxy cache enhancements

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.

1.3. Red Hat Quay configuration fields updates and changes

The following configuration fields have been added to Red Hat Quay 3.15.

1.3.1. Skopeo timeout interval

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.

Table 1.1. Skopeo timeout configuration field

Field

Type

Description

SKOPEO_TIMEOUT_INTERVAL

Integer

Number of seconds mirroring job will run before timing out.

Default: 300

Skopeo timeout example YAML

# ...
SKOPEO_TIMEOUT_INTERVAL: 300
# ...
Copy to Clipboard

For more information, see Repository mirroring.

1.3.2. Superuser configDump

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.

Table 1.2. configDump configuration field

Field

Type

Description

FEATURE_SUPERUSER_CONFIGDUMP

Boolean

Enables a full config dump of the running Framework, environment and schema for validation.

Default: false

Superuser configDump example YAML

# ...
FEATURE_SUPERUSER_CONFIGDUMP: true
# ...
Copy to Clipboard

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

1.4. API endpoint enhancements

The following API endpoints were added in Red Hat Quay 3.15.

1.4.1. Skopeo timeout interval

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).

Name

Description

Schema

skopeo_timeout_interval

Number of seconds mirroring job will run before timing out

Integer

See the createRepoMirrorConfig endpoint for more information.

1.4.2. Superuser configDump

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.

NameDescriptionSchema

configDump
optional

Returns a structured JSON dump of the current configuration, including values from config.yaml (.config), default parameters (.warning), environment variables (.env), and schema (.schema) types. Sensitive fields are obfuscated. Useful for audit/compliance validation (e.g., PCI-DSS 4.0).

object

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

1.5. Notable technical changes

The following section highlights notable technical changes for Red Hat Quay 3.15.

1.5.1. Model card rendering disabled by default

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
# ...
Copy to Clipboard

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

1.6. Known issues and limitations

The following sections note known issues and limitations for Red Hat Quay 3.15.

1.6.1. Repository mirroring known issue

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.

1.7. Future deprecations

  • The Red Hat Quay v1 UI will be deprecated in Red Hat Quay 3.16.

1.8. Red Hat Quay bug fixes

The following issues were fixed with Red Hat Quay 3.15:

  • PROJQUAY-9050. Previously, when in Tag view on the v2 UI, the Pull column was center-aligned while the other columns were left-aligned. With this release, the Pull column is left-aligned.
  • PROJQUAY-6862. Previously, when Red Hat Quay was deployed with Google Cloud Storage (GCS) as its object storage backend, pushing layers greater than 4 GiB would fail and return a 413 error. This error occurred because Red Hat Quay’s library, boto, does not support multipart uploads to GCS. This issue has been resolved, and users can now push layers greater than 4 GiB to their registry without interruption.

  • PROJQUAY-8123. Previously, if a Red Hat Quay administrator set up their deployment on a virtual machine (VM) and the administrator created the config.yaml file manually, there was a possibility that the TESTING flag was not included in the configuration. Including the TESTING: true field in the config.yaml file disables some features, such as sending emails. This is useful for developers who are testing Red Hat Quay and do not want to accidentally send out notifications or other alerts to users. When this field is not set, Red Hat Quay operates normally.

    With this update, a warning is printed upon startup, notifying the Red Hat Quay administrator that the TESTING property is either missing from the config.yaml file entirely, or that it is set to true. This alert is intended to help guide administrators towards intentional configurations for their deployment.

  • PROJQUAY-8595. Previously, Red Hat Quay would not start if Splunk had an outage. Now, Red Hat Quay pods reconcile appropriately if Splunk has an outage and, as a result, Red Hat Quay starts as intended.

1.9. Red Hat Quay feature tracker

New features have been added to Red Hat Quay, some of which are currently in Technology Preview. Technology Preview features are experimental features and are not intended for production use.

Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in Red Hat Quay, but is planned for removal in a future release and is not recommended for new deployments. For the most recent list of deprecated and removed functionality in Red Hat Quay, refer to Table 1.1. Additional details for more fine-grained functionality that has been deprecated and removed are listed after the table.

Table 1.3. Features tracker
FeatureQuay 3.15Quay 3.14Quay 3.13

Viewing model card information by using the v2 UI.

General Availability

General Availability

-

Keyless authentication with robot accounts

General Availability

General Availability

General Availability

Certificate-based authentication between Red Hat Quay and SQL

General Availability

General Availability

General Availability

FEATURE_UI_V2

Technology Preview

Technology Preview

Technology Preview

1.9.1. IBM Power, IBM Z, and IBM® LinuxONE support matrix

Table 1.4. list of supported and unsupported features
FeatureIBM PowerIBM Z and IBM® LinuxONE

Allow team synchronization via OIDC on Azure

Not Supported

Not Supported

Backing up and restoring on a standalone deployment

Supported

Supported

Clair Disconnected

Supported

Supported

Geo-Replication (Standalone)

Supported

Supported

Geo-Replication (Operator)

Supported

Not Supported

IPv6

Not Supported

Not Supported

Migrating a standalone to operator deployment

Supported

Supported

Mirror registry

Supported

Supported

Quay config editor - mirror, OIDC

Supported

Supported

Quay config editor - MAG, Kinesis, Keystone, GitHub Enterprise

Not Supported

Not Supported

Quay config editor - Red Hat Quay V2 User Interface

Supported

Supported

Quay Disconnected

Supported

Supported

Repo Mirroring

Supported

Supported

Legal Notice

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat