Add information about enabling FIPS

docs_user/assemblies/assembly_planning-the-new-deployment.adoc

@@ -25,6 +25,8 @@ include::../modules/con_about-node-selector.adoc[leveloffset=+1]
 
 include::../modules/con_about-machine-configs.adoc[leveloffset=+1]
 
+include::../modules/con_fips-support.adoc[leveloffset=+1]
+
 include::../modules/con_key-manager-service-support-for-crypto-plugins.adoc[leveloffset=+1]
 
 //include::../modules/con_identity-service-authentication.adoc[leveloffset=+1]

docs_user/modules/con_fips-support.adoc

@@ -0,0 +1,11 @@
+[id="fips-support_{context}"]
+
+= FIPS support
+
+If you are adopting an {OpenStackShort} {rhos_prev_ver} FIPS environment to {OpenStackShort} {rhos_curr_ver}, your adopted cluster will remain a FIPS cluster. There is no option to change FIPS status during adoption.
+
+There is a major difference with how FIPS was configured in {OpenStackPreviousInstaller} and how it is enabled and enforced in operator deployments. In {OpenStackPreviousInstaller} FIPS is enabled as part of its configuration, whereas in operator deployments, there is no specific FIPS configuration at the operator level.
+
+If your cluster is FIPS enabled, you must deploy a FIPS {OpenShiftShort} cluster to adopt your {OpenStackShort} {rhos_prev_ver} FIPS control plane.
+
+Enabling FIPS in {OpenShiftShort} is out of scope for this guide. Please refer to the link:https://docs.openshift.com/container-platform/latest/installing/installing-fips.html[Support for FIPS cryptography] in _OpenShift Container Platform Documentation_.