RHSA-2021:0281: Important: OpenShift Container Platform 4.4.33 bug fix and security update

Red Hat OpenShift Container Platform is Red Hat's cloud computingKubernetes application platform solution designed for on-premise or privatecloud deployments.Security Fix(es): openshift: builder allows read and write of block devices (CVE-2021-20182) kubernetes: Compromised node could escalate to cluster level privileges (CVE-2020-8559) kubernetes: Docker config secrets leaked when file is malformed and loglevel >= 4 (CVE-2020-8564) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.This advisory contains the container images for Red Hat OpenShift Container Platform 4.4.33. See the following advisory for the RPM packages for this release:https://access.redhat.com/errata/RHSA-2021:0282 Space precludes documenting all of the container images in this advisory. See the following Release Notes documentation, which will be updated shortly for this release, for details about these changes:https://docs.openshift.com/container-platform/4.4/releasenotes/ocp-4-4-release-notes.html This update fixes the following bugs among others: Previously, there were broken connections to the API server that caused nodes to remain in the NotReady state. Detecting a broken network connection could take up to 15 minutes, during which the platform would remain unavailable. This is now fixed by setting the TCPUSERTIMEOUT socket option, which controls how long transmitted data can be unacknowledged before the connection is forcefully closed. (BZ#1907939) Previously, the quota controllers only worked on resources retrieved from the discovery endpoint, which might contain only a fraction of all resources due to a network error. This is now fixed by having the quota controllers periodically resync when new resources are observed from the discovery endpoint. (BZ#1910096) Previously, the kuryr-controller was comparing security groups related to network policies incorrectly. This caused security rules related to anetwork policy to be recreated on every minor update of that networkpolicy. This bug has been fixed, allowing network policy updates thatalready have existing rules to be preserved; network policy additions ordeletions are performed, if needed. (BZ#1910221)You may download the oc tool and use it to inspect release image metadata as follows:(For x8664 architecture)$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.4.33-x8664The image digest is sha256:a035dddd8a5e5c99484138951ef4aba021799b77eb9046f683a5466c23717738(For s390x architecture)$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.4.33-s390xThe image digest is sha256:ecc1e5aaf8496dd60a7703562fd6c65541172a56ae9008fce6db5d55e43371dc(For ppc64le architecture)$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.4.33-ppc64leThe image digest is sha256:567bf8031c80b08e3e56a57e1c8e5b0b01a2f922e01b36ee333f6ab5bff95495All OpenShift Container Platform 4.4 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift Console or the CLI oc command. Instructions for upgrading a cluster are availableat https://docs.openshift.com/container-platform/4.4/updating/updating-cluster-between-minor.html#understanding-upgrade-channelsupdating-cluster-between-minor.