|
| 1 | +:_content-type: CONCEPT |
| 2 | +[id="release-notes-313"] |
| 3 | += {productname} release notes |
| 4 | + |
| 5 | +The following sections detail _y_ and _z_ stream release information. |
| 6 | + |
| 7 | +[id="rn-3-13-0"] |
| 8 | +== RHBA-2024:4525 - {productname} 3.13.0 release |
| 9 | + |
| 10 | +Issued 2024-10-zz |
| 11 | + |
| 12 | +{productname} release 3.13 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-2024:XXXX[RHBA-2024:XXXX] advisory. For the most recent compatibility matrix, see link:https://access.redhat.com/articles/4067991[Quay Enterprise 3.x Tested Integrations]. |
| 13 | + |
| 14 | +[id="release-cadence-313"] |
| 15 | +== {productname} release cadence |
| 16 | + |
| 17 | +With the release of {productname} 3.10, the product has begun to align its release cadence and lifecycle with {ocp}. As a result, {productname} releases are now generally available (GA) within approximately four weeks of the most recent version of {ocp}. Customers can not expect the support lifecycle phases of {productname} to align with {ocp} releases. |
| 18 | + |
| 19 | +For more information, see the link:https://access.redhat.com/support/policy/updates/rhquay/[{productname} Life Cycle Policy]. |
| 20 | + |
| 21 | +[id="documentation-changes-313"] |
| 22 | +== {productname} documentation changes |
| 23 | + |
| 24 | +The following documentation changes have been made with the {productname} {producty} release: |
| 25 | + |
| 26 | +* |
| 27 | + |
| 28 | +[id="new-features-and-enhancements-313"] |
| 29 | +== {productname} new features and enhancements |
| 30 | + |
| 31 | +The following updates have been made to {productname}. |
| 32 | + |
| 33 | +[id="example-feature"] |
| 34 | +=== Example feature 1 |
| 35 | + |
| 36 | +[id="example-feature-2"] |
| 37 | +=== Example Feature 2 |
| 38 | + |
| 39 | +[id="v2-ui-enhancement"] |
| 40 | +=== {productname} v2 UI enhancements |
| 41 | + |
| 42 | +The following enhancements have been made to the {productname} v2 UI. |
| 43 | + |
| 44 | +[id="example-v2-ui-enhancement"] |
| 45 | +==== Example v2 UI enhancement 2 |
| 46 | + |
| 47 | +[id="new-quay-config-fields-313"] |
| 48 | +== New {productname} configuration fields |
| 49 | + |
| 50 | +The following configuration fields have been added to {productname} {producty}. |
| 51 | + |
| 52 | +[id="oauth-reassign-configuration-field"] |
| 53 | +=== OAuth access token reassignment configuration field |
| 54 | + |
| 55 | +The following configuration field has been added for reassigning OAuth access tokens: |
| 56 | +|=== |
| 57 | +| Field | Type | Description |
| 58 | + |
| 59 | +| | | |
| 60 | +|=== |
| 61 | + |
| 62 | +.Example YAML config field |
| 63 | +[source,yaml] |
| 64 | +---- |
| 65 | +# ... |
| 66 | +yaml: true |
| 67 | +# ... |
| 68 | +---- |
| 69 | + |
| 70 | +[id="known-issues-and-limitations-313"] |
| 71 | +== {productname} 3.13 known issues and limitations |
| 72 | + |
| 73 | +The following sections note known issues and limitations for {productname} {producty}. |
| 74 | + |
| 75 | +[id="v2-ui-known-issues-313"] |
| 76 | +=== {productname} v2 UI known issues |
| 77 | + |
| 78 | +The {productname} team is aware of the following known issues on the v2 UI: |
| 79 | + |
| 80 | +* link:https://issues.redhat.com/browse/PROJQUAY-6910[*PROJQUAY-6910*]. The new UI can't group and stack the chart on usage logs |
| 81 | +* link:https://issues.redhat.com/browse/PROJQUAY-6909[*PROJQUAY-6909*]. The new UI can't toggle the visibility of the chart on usage log |
| 82 | +* link:https://issues.redhat.com/browse/PROJQUAY-6904[*PROJQUAY-6904*]. "Permanently delete" tag should not be restored on new UI |
| 83 | +* link:https://issues.redhat.com/browse/PROJQUAY-6899[*PROJQUAY-6899*]. The normal user can not delete organization in new UI when enable FEATURE_SUPERUSERS_FULL_ACCESS |
| 84 | +* link:https://issues.redhat.com/browse/PROJQUAY-6892[*PROJQUAY-6892*]. The new UI should not invoke not required stripe and status page |
| 85 | +* link:https://issues.redhat.com/browse/PROJQUAY-6884[*PROJQUAY-6884*]. The new UI should show the tip of slack Webhook URL when creating slack notification |
| 86 | +* link:https://issues.redhat.com/browse/PROJQUAY-6882[*PROJQUAY-6882*]. The new UI global readonly super user can't see all organizations and image repos |
| 87 | +* link:https://issues.redhat.com/browse/PROJQUAY-6881[*PROJQUAY-6881*]. The new UI can't show all operation types in the logs chart |
| 88 | +* link:https://issues.redhat.com/browse/PROJQUAY-6861[*PROJQUAY-6861*]. The new UI "Last Modified" of organization always show N/A after target organization's setting is updated |
| 89 | +* link:https://issues.redhat.com/browse/PROJQUAY-6860[*PROJQUAY-6860*]. The new UI update the time machine configuration of organization show NULL in usage logs |
| 90 | +* link:https://issues.redhat.com/browse/PROJQUAY-6859[*PROJQUAY-6859*]. Thenew UI remove image repo permission show "undefined" for organization name in audit logs |
| 91 | +* link:https://issues.redhat.com/browse/PROJQUAY-6852[*PROJQUAY-6852*]. "Tag manifest with the branch or tag name" option in build trigger setup wizard should be checked by default. |
| 92 | +* link:https://issues.redhat.com/browse/PROJQUAY-6832[*PROJQUAY-6832*]. The new UI should validate the OIDC group name when enable OIDC Directory Sync |
| 93 | +* link:https://issues.redhat.com/browse/PROJQUAY-6830[*PROJQUAY-6830*]. The new UI should show the sync icon when the team is configured sync team members from OIDC Group |
| 94 | +* link:https://issues.redhat.com/browse/PROJQUAY-6829[*PROJQUAY-6829*]. The new UI team member added to team sync from OIDC group should be audited in Organization logs page |
| 95 | +* link:https://issues.redhat.com/browse/PROJQUAY-6825[*PROJQUAY-6825*]. Build cancel operation log can not be displayed correctly in new UI |
| 96 | +* link:https://issues.redhat.com/browse/PROJQUAY-6812[*PROJQUAY-6812*]. The new UI the "performer by" is NULL of build image in logs page |
| 97 | +* link:https://issues.redhat.com/browse/PROJQUAY-6810[*PROJQUAY-6810*]. The new UI should highlight the tag name with tag icon in logs page |
| 98 | +* link:https://issues.redhat.com/browse/PROJQUAY-6808[*PROJQUAY-6808*]. The new UI can't click the robot account to show credentials in logs page |
| 99 | +* link:https://issues.redhat.com/browse/PROJQUAY-6807[*PROJQUAY-6807*]. The new UI can't see the operations types in log page when quay is in dark mode |
| 100 | +* link:https://issues.redhat.com/browse/PROJQUAY-6770[*PROJQUAY-6770*]. The new UI build image by uploading Docker file should support .tar.gz or .zip |
| 101 | +* link:https://issues.redhat.com/browse/PROJQUAY-6769[*PROJQUAY-6769*]. The new UI should not display message "Trigger setup has already been completed" after build trigger setup completed |
| 102 | +* link:https://issues.redhat.com/browse/PROJQUAY-6768[*PROJQUAY-6768*]. The new UI can't navigate back to current image repo from image build |
| 103 | +* link:https://issues.redhat.com/browse/PROJQUAY-6767[*PROJQUAY-6767*]. The new UI can't download build logs |
| 104 | +* link:https://issues.redhat.com/browse/PROJQUAY-6758[*PROJQUAY-6758*]. The new UI should display correct operation number when hover over different operation type |
| 105 | +* link:https://issues.redhat.com/browse/PROJQUAY-6757[*PROJQUAY-6757*]. The new UI usage log should display the tag expiration time as date format |
| 106 | + |
| 107 | +[id="limitations-313"] |
| 108 | +=== {productname} 3.13 limitations |
| 109 | + |
| 110 | + |
| 111 | +[id="bug-fixes-313"] |
| 112 | +== {productname} bug fixes |
| 113 | + |
| 114 | +The following issues were fixed with {productname} {producty}: |
| 115 | + |
| 116 | +[id="quay-feature-tracker"] |
| 117 | +== {productname} feature tracker |
| 118 | + |
| 119 | +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. |
| 120 | + |
| 121 | +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. |
| 122 | + |
| 123 | +//Remove entries with the same status older than the latest three releases. |
| 124 | + |
| 125 | +.New features tracker |
| 126 | +[cols="4,1,1,1",options="header"] |
| 127 | +|=== |
| 128 | +|Feature | Quay 3.13 | Quay 3.12 | Quay 3.11 |
| 129 | + |
| 130 | +|link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#proc_manage-log-storage-splunk[Splunk HTTP Event Collector (HEC)] support |
| 131 | +|General Availability |
| 132 | +|General Availability |
| 133 | +|- |
| 134 | + |
| 135 | +|link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html/use_red_hat_quay/index#oci-intro[Open Container Initiative 1.1 support] |
| 136 | +|General Availability |
| 137 | +|General Availability |
| 138 | +|- |
| 139 | + |
| 140 | +|link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/use_red_hat_quay/index#reassigning-oauth-access-token[Reassigning an OAuth access token] |
| 141 | +|General Availability |
| 142 | +|General Availability |
| 143 | +|- |
| 144 | + |
| 145 | +|link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html/use_red_hat_quay/index#creating-image-expiration-notification[Creating an image expiration notification] |
| 146 | +|General Availability |
| 147 | +|General Availability |
| 148 | +|- |
| 149 | + |
| 150 | +|link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#oidc-team-sync[Team synchronization for {productname} OIDC deployments] |
| 151 | +|General Availability |
| 152 | +|General Availability |
| 153 | +|General Availability |
| 154 | + |
| 155 | +| link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#configuring-resources-managed-components[Configuring resources for managed components on {ocp}] |
| 156 | +|General Availability |
| 157 | +|General Availability |
| 158 | +|General Availability |
| 159 | + |
| 160 | +|link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#configuring-aws-sts-quay[Configuring AWS STS for {productname}], link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_operator_features/index#configuring-aws-sts-quay[Configuring AWS STS for {productname-ocp}] |
| 161 | +|General Availability |
| 162 | +|General Availability |
| 163 | +|General Availability |
| 164 | + |
| 165 | +|link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html/manage_red_hat_quay/red-hat-quay-namespace-auto-pruning-overview[{productname} repository auto-pruning] |
| 166 | +|General Availability |
| 167 | +|General Availability |
| 168 | +|General Availability |
| 169 | + |
| 170 | +|link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/use_red_hat_quay/index#configuring-dark-mode-ui[Configuring dark mode on the {productname} v2 UI] |
| 171 | +|General Availability |
| 172 | +|General Availability |
| 173 | +|General Availability |
| 174 | + |
| 175 | +|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] |
| 176 | +|Technology Preview |
| 177 | +|Technology Preview |
| 178 | +|Technology Preview |
| 179 | + |
| 180 | +|=== |
| 181 | + |
| 182 | +[id="ibm-power-z-linuxone-support-matrix"] |
| 183 | +=== IBM Power, IBM Z, and IBM® LinuxONE support matrix |
| 184 | + |
| 185 | +.list of supported and unsupported features |
| 186 | +[cols="3,1,1",options="header"] |
| 187 | +|=== |
| 188 | +|Feature |IBM Power |IBM Z and IBM(R) LinuxONE |
| 189 | + |
| 190 | +|Allow team synchronization via OIDC on Azure |
| 191 | +|Not Supported |
| 192 | +|Not Supported |
| 193 | + |
| 194 | +|Backing up and restoring on a standalone deployment |
| 195 | +|Supported |
| 196 | +|Supported |
| 197 | + |
| 198 | +|Clair Disconnected |
| 199 | +|Supported |
| 200 | +|Supported |
| 201 | + |
| 202 | +|Geo-Replication (Standalone) |
| 203 | +|Supported |
| 204 | +|Supported |
| 205 | + |
| 206 | +|Geo-Replication (Operator) |
| 207 | +|Not Supported |
| 208 | +|Not Supported |
| 209 | + |
| 210 | +|IPv6 |
| 211 | +|Not Supported |
| 212 | +|Not Supported |
| 213 | + |
| 214 | +|Migrating a standalone to operator deployment |
| 215 | +|Supported |
| 216 | +|Supported |
| 217 | + |
| 218 | +|Mirror registry |
| 219 | +|Not Supported |
| 220 | +|Not Supported |
| 221 | + |
| 222 | +|PostgreSQL connection pooling via pgBouncer |
| 223 | +|Supported |
| 224 | +|Supported |
| 225 | + |
| 226 | +|Quay config editor - mirror, OIDC |
| 227 | +|Supported |
| 228 | +|Supported |
| 229 | + |
| 230 | +|Quay config editor - MAG, Kinesis, Keystone, GitHub Enterprise |
| 231 | +|Not Supported |
| 232 | +|Not Supported |
| 233 | + |
| 234 | +|Quay config editor - Red Hat Quay V2 User Interface |
| 235 | +|Supported |
| 236 | +|Supported |
| 237 | + |
| 238 | +|Quay Disconnected |
| 239 | +|Supported |
| 240 | +|Supported |
| 241 | + |
| 242 | +|Repo Mirroring |
| 243 | +|Supported |
| 244 | +|Supported |
| 245 | +|=== |
0 commit comments