mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
fixing PV1 build
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
258419ab06
commit
cdea3b51b6
@@ -114,4 +114,4 @@ include::modules/oc-mirror-imageset-config-parameters-v2.adoc[leveloffset=+1]
|
||||
|
||||
// Command reference for oc-mirror v2
|
||||
include::modules/oc-mirror-command-reference-v2.adoc[leveloffset=+1]
|
||||
* xref:../../installing/disconnected_install/about-installing-oc-mirror-v2.adoc#oc-mirror-updating-cluster-manifests-v2_installing-mirroring-disconnected[Configuring your cluster to use the resources generated by oc-mirror]
|
||||
* xref:../../installing/disconnected_install/about-installing-oc-mirror-v2.adoc#oc-mirror-updating-cluster-manifests-v2_about-installing-oc-mirror-v2[Configuring your cluster to use the resources generated by oc-mirror]
|
||||
|
||||
@@ -94,7 +94,12 @@ ifndef::openshift-origin[]
|
||||
<11> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
|
||||
+
|
||||
--
|
||||
include::snippets/fips-snippet.adoc[]
|
||||
[IMPORTANT]
|
||||
====
|
||||
To enable FIPS mode for your cluster, you must run the installation program from a {op-system-base-full} computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/assembly_installing-the-system-in-fips-mode_security-hardening[Installing the system in FIPS mode].
|
||||
|
||||
When running {op-system-base-full} or {op-system-first} booted in FIPS mode, {product-title} core components use the {op-system-base} cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.
|
||||
====
|
||||
--
|
||||
<12> If your Azure Stack Hub environment uses an internal certificate authority (CA), add the necessary certificate bundle in `.pem` format.
|
||||
<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
|
||||
|
||||
@@ -217,7 +217,12 @@ ifndef::openshift-origin[]
|
||||
<13> Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
|
||||
+
|
||||
--
|
||||
include::snippets/fips-snippet.adoc[]
|
||||
[IMPORTANT]
|
||||
====
|
||||
To enable FIPS mode for your cluster, you must run the installation program from a {op-system-base-full} computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/assembly_installing-the-system-in-fips-mode_security-hardening[Installing the system in FIPS mode].
|
||||
|
||||
When running {op-system-base-full} or {op-system-first} booted in FIPS mode, {product-title} core components use the {op-system-base} cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.
|
||||
====
|
||||
--
|
||||
<14> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
|
||||
endif::openshift-origin[]
|
||||
|
||||
@@ -94,7 +94,12 @@ ifndef::openshift-origin[]
|
||||
<6> Enables or disables FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the {op-system-first} machines that {product-title} runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with {op-system} instead.
|
||||
+
|
||||
--
|
||||
include::snippets/fips-snippet.adoc[]
|
||||
[IMPORTANT]
|
||||
====
|
||||
To enable FIPS mode for your cluster, you must run the installation program from a {op-system-base-full} computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/assembly_installing-the-system-in-fips-mode_security-hardening[Installing the system in FIPS mode].
|
||||
|
||||
When running {op-system-base-full} or {op-system-first} booted in FIPS mode, {product-title} core components use the {op-system-base} cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.
|
||||
====
|
||||
--
|
||||
<7> Optional: provide the `sshKey` value that you use to access the machines in your cluster.
|
||||
endif::openshift-origin[]
|
||||
|
||||
Reference in New Issue
Block a user