First published: Mon Feb 01 2021(Updated: )
Red Hat OpenShift Container Platform is Red Hat's cloud computing<br>Kubernetes application platform solution designed for on-premise or private<br>cloud deployments.<br>This advisory contains the container images for Red Hat OpenShift Container<br>Platform 4.6.15. See the following advisory for the RPM packages for this<br>release:<br><a href="https://access.redhat.com/errata/RHBA-2021:0237" target="_blank">https://access.redhat.com/errata/RHBA-2021:0237</a> Space precludes documenting all of the container images in this advisory.<br>See the following Release Notes documentation, which will be updated<br>shortly for this release, for details about these changes:<br><a href="https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html" target="_blank">https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html</a> This update fixes the following bugs among others:<br><li> When installing on AWS previously, the Cloud Credential Operator automatically created an OpenID discovery endpoint that could be used to externally authenticate service account tokens obtained with the TokenRequest API. This involved changing the `serviceAccountIssuer` on the kube-apiserver, which invalidated any previously minted tokens. This functionality has been removed. Creation and configuration of the OpenID discovery endpoint and `serviceAccountIssuer` now must be done by the cluster admin at cluster installation time. The `serviceAccountIssuer` can no longer be changed after cluster installation begins. (BZ#1907613)</li> <li> Previously, the log level for the kube-rbac-proxy was set to level 10. This caused excessive detail in the log messages for the kube-rbac-proxy. The log level for the kube-rbac-proxy has been decreased to 3 to match other components, resulting in more appropriate logging detail for most scenarios. (BZ#1908316)</li> <li> Previously, a missing guard in the Red Hat OpenStack Platform (RHOSP) validations could have led to fetching the list of subnets with an empty subnet ID, and caused some non-RHOSP clouds to return unexpected values. The unexpected error code would fail validation and prevent a cluster installation on these non-RHOSP clouds. This has been fixed by adding the missing guard against empty subnet ID. This validation now returns the expected result, allowing a cluster to be installed on more clouds. (BZ#1913813)</li> You may download the oc tool and use it to inspect release image metadata as follows:<br>(For x86_64 architecture)<br>$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.6.15-x86_64<br>The image digest is sha256:b70f550e3fa94af2f7d60a3437ec0275194db36f2dc49991da2336fe21e2824c<br>(For s390x architecture)<br>$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.6.15-s390x<br>The image digest is sha256:4f113aa813f96701ea62474bcaa5545451a9cbfbdf3437fa9c24f8a8ac288010<br>(For ppc64le architecture)<br>$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.6.15-ppc64le<br>The image digest is sha256:ef0937ce67e3cc8eafbb613a90ea4434330ae2b2546d0291c164242ef87d67a8<br>All OpenShift Container Platform 4.6 users are advised to upgrade to these<br>updated packages and images when they are available in the appropriate<br>release channel. To check for available updates, use the OpenShift Console<br>or the CLI oc command. Instructions for upgrading a cluster are available<br>at<br><a href="https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor." target="_blank">https://docs.openshift.com/container-platform/4.6/updating/updating-cluster-between-minor.html#understanding-upgrade-channels_updating-cluster-between-minor.</a>
Affected Software | Affected Version | How to fix |
---|
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.