Skip to content

Commit 4e15daa

Browse files
stevsmitSteven Smith
stevsmit
and
Steven Smith
authored
Modularize rns 315 (quay#1445)
* modularizes 3.15 release notes * Modularizes RNs 3.15 --------- Co-authored-by: Steven Smith <[email protected]>
1 parent aa9d394 commit 4e15daa

15 files changed

+341
-331
lines changed

‎modules/bug-fixes-315.adoc‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="bug-fixes-315"]
3+
= {productname} bug fixes
4+
5+
The following issues were fixed with {productname} 3.15:
6+
7+
* link:https://issues.redhat.com/browse/PROJQUAY-9050[*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.
8+
9+
* link:https://issues.redhat.com/browse/PROJQUAY-6862[*PROJQUAY-6862*]. Previously, when {productname} 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 {productname}'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.
10+
11+
* link:https://issues.redhat.com/browse/PROJQUAY-8123[*PROJQUAY-8123*]. Previously, if a {productname} 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 {productname} and do not want to accidentally send out notifications or other alerts to users. When this field is not set, {productname} operates normally.
12+
+
13+
With this update, a warning is printed upon startup, notifying the {productname} 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.
14+
15+
* link:https://issues.redhat.com/browse/PROJQUAY-8595[*PROJQUAY-8595*]. Previously, {productname} would not start if Splunk had an outage. Now, {productname} pods reconcile appropriately if Splunk has an outage and, as a result, {productname} starts as intended.

‎modules/deprecations-315.adoc‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="deprecations-315"]
3+
= Future deprecations
4+
5+
The {productname} v1 UI will be deprecated in {productname} 3.16.

‎modules/documentation-changes-315.adoc‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="documentation-changes-315"]
3+
= {productname} documentation changes
4+
5+
The following documentation changes have been made with the {productname} 3.15 release:
6+
7+
* The link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html/configure_red_hat_quay[Configure {productname}] book has been refactored. This book now provides expanded information on the following topics:
8+
9+
** Understanding the {productname} configuration file
10+
** On premise {productname} configuration overview
11+
** {productname-ocp} configuration overview, including the `QuayRegistry` custom resource
12+
13+
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.

‎modules/known-issues-and-limitations-315.adoc‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="known-issues-and-limitations-315"]
3+
= Known issues and limitations
4+
5+
The following sections note known issues and limitations for {productname} 3.15.
6+
7+
[id="repository-mirroring-known-issue"]
8+
== Repository mirroring known issue
9+
10+
There is a known issue affecting the mirroring feature of {productname}. 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 {productname}.

‎modules/new-api-endpoints-315.adoc‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="new-api-endpoints-315"]
3+
= API endpoint enhancements
4+
5+
The following API endpoints were added in {productname} 3.15.
6+
7+
[id="skopeo-timeout-api-endpoint"]
8+
== Skopeo timeout interval
9+
10+
A new parameter, `SKOPEO_TIMEOUT_INTERVAL`, has been added to the `createRepoMirrorConfig` endpoint. This parameter allows {productname} 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).
11+
12+
|===
13+
| Name | Description | Schema
14+
|*skopeo_timeout_interval* |Number of seconds mirroring job will run before timing out | Integer
15+
|===
16+
17+
See the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html/red_hat_quay_api_reference/mirror#createrepomirrorconfig[createRepoMirrorConfig] endpoint for more information.
18+
19+
[id="api-v1-superuser-config"]
20+
== Superuser configDump
21+
22+
A new superuser API parameter, `v1/superuser/config`, has been added to the {productname} 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.
23+
24+
|===
25+
|Name|Description|Schema
26+
27+
|**configDump** +
28+
_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
29+
30+
|===
31+
32+
For example API commands, see link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_reference/index#superuser[Red Hat Quay API superuser commands].

‎modules/new-features-and-enhancements-315.adoc‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="new-features-and-enhancements-315"]
3+
= {productname} new features and enhancements
4+
5+
The following updates have been made to {productname}.
6+
7+
[id="v2-ui-notification-drawer"]
8+
== v2 UI notification drawer
9+
10+
With this release, a _notification drawer_ has been added to the {productname} 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.
11+
12+
[NOTE]
13+
====
14+
Currently, the v2 UI does not support the *{productname} Notification* option when selecting a notification method. You can select the *{productname} Notification* method by using the v1 UI.
15+
====
16+
17+
[id="proxy-cache-enhancements"]
18+
== Proxy cache enhancements
19+
20+
Previously, when pulling from a proxied repository, only the layers explicitly requested by the client were cached in the {productname} registry. This behavior stemmed from {productname} 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 {productname} 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.
21+
22+
With this release, {productname} 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.

‎modules/new-quay-config-fields-315.adoc‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="new-quay-config-fields-315"]
3+
= {productname} configuration fields updates and changes
4+
5+
The following configuration fields have been added to {productname} 3.15.
6+
7+
[id="skopeo-timeout-configuration-field"]
8+
== Skopeo timeout interval
9+
10+
The `SKOPEO_TIMEOUT_INTERVAL` configuration field has been added. With this field, {productname} 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.
11+
12+
.Skopeo timeout configuration field
13+
|===
14+
| Field | Type | Description
15+
|*SKOPEO_TIMEOUT_INTERVAL* |Integer | Number of seconds mirroring job will run before timing out. +
16+
+
17+
**Default:** `300`
18+
|===
19+
20+
.Skopeo timeout example YAML
21+
[source,yaml]
22+
----
23+
# ...
24+
SKOPEO_TIMEOUT_INTERVAL: 300
25+
# ...
26+
----
27+
28+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#repo-mirroring-in-red-hat-quay[Repository mirroring].
29+
30+
[id="superuser-config-dump"]
31+
== Superuser configDump
32+
33+
The `FEATURE_SUPERUSER_CONFIGDUMP` configuration field has been added. With this field, {productname} 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.
34+
35+
.configDump configuration field
36+
|===
37+
| Field | Type | Description
38+
|*FEATURE_SUPERUSER_CONFIGDUMP* |Boolean | Enables a full config dump of the running Framework, environment and schema for validation. +
39+
+
40+
**Default:** `False`
41+
|===
42+
43+
.Superuser configDump example YAML
44+
[source,yaml]
45+
----
46+
# ...
47+
FEATURE_SUPERUSER_CONFIGDUMP: true
48+
# ...
49+
----
50+
51+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/configure_red_hat_quay/index#retrieving-config-file-api[Retrieving the configuration file by using the API].

‎modules/notable-technical-changes-315.adoc‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
:_mod-docs-content-type: REFERENCE
2+
[id="notable-technical-changes-315"]
3+
= Notable technical changes
4+
5+
The following section highlights notable technical changes for {productname} 3.15.
6+
7+
[id="model-card-disable"]
8+
== Model card rendering disabled by default
9+
10+
In {productname} 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.
11+
12+
With {productname} 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:
13+
14+
[source,yaml]
15+
----
16+
# ...
17+
FEATURE_UI_MODELCARD: true
18+
# ...
19+
----
20+
21+
This change will be reverted in a future version of {productname}.

‎modules/quay-feature-tracker.adoc‎

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
:_mod-docs-content-type: REFERENCE
2+
3+
[id="quay-feature-tracker"]
4+
= {productname} feature tracker
5+
6+
New features have been added to {productname}, some of which are currently in Technology Preview. Technology Preview features are experimental features and are not intended for production use.
7+
8+
Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in {productname}, 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 {productname}, refer to Table 1.1. Additional details for more fine-grained functionality that has been deprecated and removed are listed after the table.
9+
10+
//Remove entries with the same status older than the latest three releases.
11+
12+
.Features tracker
13+
[cols="4,1,1,1",options="header"]
14+
|===
15+
|Feature | Quay 3.15 | Quay 3.14 | Quay 3.13
16+
17+
|link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/use_red_hat_quay/index#viewing-model-card-information[Viewing model card information by using the v2 UI].
18+
|General Availability
19+
|General Availability
20+
|-
21+
22+
|link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#keyless-authentication-robot-accounts[Keyless authentication with robot accounts]
23+
|General Availability
24+
|General Availability
25+
|General Availability
26+
27+
|link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/securing_red_hat_quay/index#cert-based-auth-quay-sql[Certificate-based authentication between {productname} and SQL]
28+
|General Availability
29+
|General Availability
30+
|General Availability
31+
32+
|link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.8/html-single/configure_red_hat_quay/index#reference-miscellaneous-v2-ui[FEATURE_UI_V2]
33+
|Technology Preview
34+
|Technology Preview
35+
|Technology Preview
36+
37+
|===
38+
39+
[id="ibm-power-z-linuxone-support-matrix"]
40+
== IBM Power, IBM Z, and IBM® LinuxONE support matrix
41+
42+
.list of supported and unsupported features
43+
[cols="3,1,1",options="header"]
44+
|===
45+
|Feature |IBM Power |IBM Z and IBM(R) LinuxONE
46+
47+
|Allow team synchronization via OIDC on Azure
48+
|Not Supported
49+
|Not Supported
50+
51+
|Backing up and restoring on a standalone deployment
52+
|Supported
53+
|Supported
54+
55+
|Clair Disconnected
56+
|Supported
57+
|Supported
58+
59+
|Geo-Replication (Standalone)
60+
|Supported
61+
|Supported
62+
63+
|Geo-Replication (Operator)
64+
|Supported
65+
|Not Supported
66+
67+
|IPv6
68+
|Not Supported
69+
|Not Supported
70+
71+
|Migrating a standalone to operator deployment
72+
|Supported
73+
|Supported
74+
75+
|Mirror registry
76+
|Supported
77+
|Supported
78+
79+
|Quay config editor - mirror, OIDC
80+
|Supported
81+
|Supported
82+
83+
|Quay config editor - MAG, Kinesis, Keystone, GitHub Enterprise
84+
|Not Supported
85+
|Not Supported
86+
87+
|Quay config editor - Red Hat Quay V2 User Interface
88+
|Supported
89+
|Supported
90+
91+
|Quay Disconnected
92+
|Supported
93+
|Supported
94+
95+
|Repo Mirroring
96+
|Supported
97+
|Supported
98+
|===

‎modules/rn-3-15-0.adoc‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
2+
:_mod-docs-content-type: REFERENCE
3+
4+
[id="rn-3-15-0"]
5+
= RHBA-2025:8408 - {productname} 3.15.0 release
6+
7+
Issued 2025-07-07
8+
9+
{productname} release {producty} is now available with Clair {clairproductminv}. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2025:9240[RHBA-2025:9240] advisory. For the most recent compatibility matrix, see link:https://access.redhat.com/articles/4067991[Quay Enterprise 3.x Tested Integrations]. For information on the release cadence of {productname}, see the link:https://access.redhat.com/support/policy/updates/rhquay/[{productname} Life Cycle Policy].

0 commit comments

Comments
 (0)