FIPS validation in Red Hat OpenShift Container Platform
Red Hat OpenShift Container Platform uses certain FIPS validated or Modules In Process modules within RHEL and RHCOS for the operating system components that it uses.
For more information, see "RHEL core crypto components" in the Additional resources section. For example, when users use SSH to connect to Red Hat OpenShift Container Platform clusters and containers, those connections are properly encrypted.
Red Hat OpenShift Container Platform components are written in Go and built with Red Hat’s golang compiler. When you enable FIPS mode for your cluster, all Red Hat OpenShift Container Platform components that require cryptographic signing call RHEL and RHCOS cryptographic libraries.
| Attributes | Limitations |
|---|---|
FIPS support in RHEL 9 and RHCOS operating systems. |
The FIPS implementation does not use a function that performs hash computation and signature generation or validation in a single step. This limitation will continue to be evaluated and improved in future Red Hat OpenShift Container Platform releases. |
FIPS support in CRI-O runtimes. |
|
FIPS support in Red Hat OpenShift Container Platform services. |
|
FIPS validated or Modules In Process cryptographic module and algorithms that are obtained from RHEL 9 and RHCOS binaries and images. |
|
Use of FIPS compatible golang compiler. |
TLS FIPS support is not complete but is planned for future Red Hat OpenShift Container Platform releases. |
FIPS support across multiple architectures. |
FIPS is currently only supported on Red Hat OpenShift Container Platform deployments using |