// Module included in the following assembly:
// installing/installing-fips.adoc

:_mod-docs-content-type: REFERENCE
[id="installation-about-fips-validation_{context}"]
= FIPS validation in {product-title}

[role="_abstract"]
{product-title} uses certain FIPS validated or Modules In Process modules within {op-system-base} and {op-system} 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 {product-title} clusters and containers, those connections are properly encrypted.

{product-title} components are written in Go and built with Red Hat's golang compiler. When you enable FIPS mode for your cluster, all {product-title} components that require cryptographic signing call {op-system-base} and {op-system} cryptographic libraries.

.FIPS mode attributes and limitations in {product-title} {product-version}
[cols="8a,8a",options="header"]
|===

|Attributes
|Limitations

|FIPS support in {op-system-base} 9 and {op-system} operating systems.
.4+|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 {product-title} releases.

|FIPS support in CRI-O runtimes.
|FIPS support in {product-title} services.
|FIPS validated or Modules In Process cryptographic module and algorithms that are obtained from {op-system-base} 9 and {op-system} binaries and images.

|Use of FIPS compatible golang compiler.
|TLS FIPS support is not complete but is planned for future {product-title} releases.

|FIPS support across multiple architectures.
|FIPS is currently only supported on {product-title} deployments using `x86_64`, `ppc64le`, and `s390x` architectures.

|===
