From 440485f0edbba0ebe1f0f71a71d9ec428e047979 Mon Sep 17 00:00:00 2001 From: emarcusRH Date: Wed, 29 Mar 2023 16:05:14 +0300 Subject: [PATCH] new pr to update config yaml in 4_11 installation --- modules/installation-bare-metal-config-yaml.adoc | 8 -------- 1 file changed, 8 deletions(-) diff --git a/modules/installation-bare-metal-config-yaml.adoc b/modules/installation-bare-metal-config-yaml.adoc index 3c7dac6d584c..bf082d66defa 100644 --- a/modules/installation-bare-metal-config-yaml.adoc +++ b/modules/installation-bare-metal-config-yaml.adoc @@ -257,14 +257,6 @@ ifdef::ibm-z,ibm-z-kvm[IBM Z infrastructure.] ifdef::ibm-power[IBM Power infrastructure.] ifdef::rhv[RHV infrastructure.] ifndef::openshift-origin[] -+ -[WARNING] -==== -Red Hat Virtualization does not currently support installation with user-provisioned infrastructure on the oVirt platform. Therefore, you must set the platform to `none`, allowing {product-title} to identify each node as a bare-metal node and the cluster as a bare-metal cluster. This is the same as xref:../../installing/installing_platform_agnostic/installing-platform-agnostic.adoc#installing-platform-agnostic[installing a cluster on any platform], and has the following limitations: - -. There will be no cluster provider so you must manually add each machine and there will be no node scaling capabilities. -. The oVirt CSI driver will not be installed and there will be no CSI capabilities. -==== <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. + [IMPORTANT]