Chapter 1. About this release
These release notes track the development of Red Hat OpenShift sandboxed containers 1.13 for Red Hat OpenShift Container Platform 4.22. Release notes include links to the original tickets. Private tickets have no links.
1.1. FIPS compliance Copy linkLink copied to clipboard!
OpenShift Container Platform is designed for Federal Information Processing Standards (FIPS) 140-2 and 140-3. When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.
OpenShift sandboxed containers can be used on FIPS-enabled clusters.
When running in FIPS mode, OpenShift sandboxed containers components, virtual machines (VMs), and VM images are adapted to comply with FIPS.
FIPS compliance for OpenShift sandboxed containers only applies to the kata runtime class. The peer pod runtime class, kata-remote, is not yet fully supported and has not been tested for FIPS compliance.
1.2. PQC compliance Copy linkLink copied to clipboard!
OpenShift Container Platform supports post-quantum cryptography (PQC) readiness for secure cluster communication. When running on Red Hat Enterprise Linux (RHEL) , core OpenShift Container Platform components use the cryptographic capabilities provided by the platform operating system and TLS 1.3 security profiles, including hybrid Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) key exchange where enabled by the configured TLS security profile and supported by the component.