Known issue 311 (#932)

modules/proc_use-quay-build-workers-dockerfiles.adoc

@@ -87,7 +87,7 @@ $ oc get sa openshift-apiserver-sa --namespace=openshift-apiserver -o json | jq
 
 .. Obtain the `ca.crt` key value from the secret in the {ocp} Web Console. The value begins with *"-----BEGIN CERTIFICATE-----"`*. 
 
-.. Import the CA in {productname} using the Config Tool. Ensure that the name of this file matches `K8S_API_TLS_CA`. 
+.. Import the CA to {productname}. Ensure that the name of this file matches `K8S_API_TLS_CA`. 
 
 . Create the following `SecurityContextConstraints` resource for the `ServiceAccount`:
 +
@@ -170,11 +170,6 @@ FEATURE_BUILD_SUPPORT: True
 
 . Add the following information to your {productname} `config.yaml` file, replacing each value with information that is relevant to your specific installation:
 +
-[NOTE]
-====
-Currently, only the Build feature itself can be enabled by the {productname} Config Tool. The configuration of the Build Manager and Executors must be done manually in the `config.yaml` file.
-====
-+
 [source,yaml]
 ----
 BUILD_MANAGER:

modules/rn_3_11_0.adoc

@@ -183,6 +183,11 @@ Currently, when an OIDC user is removed from their OIDC provider, the user is no
 
 When using Microsoft Entra ID as your OIDC provider, {productname} administrators must input the *Object ID* of the OIDC group instead of the group name. The v2 UI does not currently alert users that Microsoft Entra ID users must input the Object ID of the OIDC group. This is a known issue and will be fixed in a future version of {productname}. (link:https://issues.redhat.com/browse/PROJQUAY-6917[*PROJQUAY-6917*])
 
+[id="sts-s3-storage-known-issue"]
+=== STS S3 storage known issue
+
+When using Amazon Web Services (AWS) Security Token Service (STS) with proxy storage enabled, users are unable to pull images and the following error is returned: `Error: copying system image from manifest list: parsing image configuration: fetching blob: received unexpected HTTP status: 502 Bad Gateway`. This is a known issue and will be fixed in a future version of {productname}.
+
 [id="upgrading-38-311-limitation"]
 === Upgrading {productname-ocp} 3.8 directly to 3.11 limitation
 
@@ -195,7 +200,6 @@ For more information, see link:https://access.redhat.com/documentation/en-us/red
 
 Attempting to set resource limitations for the `Quay` pod too low results in the pod being unable to boot up with the following statuses returned: `OOMKILLED` and `CrashLoopBackOff`. Resource limitations can not be set lower than the minimum requirement, which can be found on the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#configuring-resources-managed-components[Configuring resources for managed components on {ocp}] page.
 
-
 [id="v2-ui-known-issues-311"]
 === {productname} v2 UI known issues
 
@@ -234,8 +238,6 @@ The {productname} team is aware of the following known issues on the v2 UI:
 ==== {productname} v2 UI dark mode known issue
 
 If you are using the the automatic mode selection, which chooses between light or dark modes depending on the user's browser preference, your operating system appearance is overridden by the browser website appearance setting. If you find that the device-based theme is not working as expect, check your browser appearance setting. This is a known issue and will be fixed in a future version of {productname}. (link:https://issues.redhat.com/browse/PROJQUAY-6903[*PROJQUAY-6903*])
-//* link:[**].
-
 
 ////
 
@@ -286,6 +288,11 @@ The following technical changes have been made to {productname} in 3.11.
 
 {productname} 3.11 does not support PgBouncer.
 
+[id="power-z-linuxone-support-matrix-changes"]
+=== IBM Power, IBM Z, and IBM® LinuxONE support matrix changes
+
+Support has changed for some IBM Power, IBM Z, and IBM® LinuxONE features. For more information, see the "IBM Power, IBM Z, and IBM® LinuxONE support matrix" table.
+
 [id="bug-fixes-311"]
 == {productname} bug fixes