||The base domain of the cluster. All DNS records must be sub-domains of this
base and include the cluster name.
controlPlane section is a single mapping, but the
compute section is a sequence of mappings. To meet the requirements of the different data structures, the first line of the
compute section must begin with a hyphen,
-, and the first line of the
controlPlane section must not. Only one control plane pool is used.
||Whether to enable or disable simultaneous multithreading (SMT), or
hyperthreading. By default, SMT is enabled to increase the performance of your machines' cores. You can disable it by setting the parameter value to
Disabled. If you disable SMT, you must disable it in all cluster machines; this includes both control plane and compute machines.
Simultaneous multithreading (SMT) is enabled by default. If SMT is not enabled in your BIOS settings, the
hyperthreading parameter has no effect.
If you disable
hyperthreading, whether in the BIOS or in the
install-config.yaml, ensure that your capacity planning accounts for the dramatically decreased machine performance.
||You must set the value of the
replicas parameter to
0. This parameter
controls the number of workers that the cluster creates and manages for you,
which are functions that the cluster does not perform when you
use user-provisioned infrastructure. You must manually deploy worker
machines for the cluster to use before you finish installing OpenShift Container Platform.
||The number of control plane machines that you add to the cluster. Because
the cluster uses these values as the number of etcd endpoints in the cluster, the
value must match the number of control plane machines that you deploy.
||The cluster name that you specified in your DNS records.
||A block of IP addresses from which pod IP addresses are allocated. This block must not overlap with existing physical networks. These IP addresses are used for the pod network. If you need to access the pods from an external network, you must configure load balancers and routers to manage the traffic.
Class E CIDR range is reserved for a future use. To use the Class E CIDR range, you must ensure your networking environment accepts the IP addresses within the Class E CIDR range.
||The subnet prefix length to assign to each individual node. For example, if
hostPrefix is set to
23, then each node is assigned a
/23 subnet out of
cidr, which allows for 510 (2^(32 - 23) - 2) pod IPs addresses. If
you are required to provide access to nodes from an external network, configure
load balancers and routers to manage the traffic.
||The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.
||You must set the platform to
none. You cannot provide additional platform configuration variables for
IBM Power Systems infrastructure.
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 OpenShift Container Platform to identify each node as a bare-metal node and the cluster as a bare-metal cluster. This is the same as 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.
||Whether to enable or disable FIPS mode. By default, FIPS mode is not enabled. If FIPS mode is enabled, the Red Hat Enterprise Linux CoreOS (RHCOS) machines that OpenShift Container Platform runs on bypass the default Kubernetes cryptography suite and use the cryptography modules that are provided with RHCOS instead.
The use of FIPS Validated / Modules in Process cryptographic libraries is only supported on OpenShift Container Platform deployments on the
<local_registry>, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example,
<credentials>, specify the base64-encoded user name and password for your mirror registry.
||The public portion of the default SSH key for the
core user in
Red Hat Enterprise Linux CoreOS (RHCOS).
For production OpenShift Container Platform clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your
ssh-agent process uses.
||Provide the contents of the certificate file that you used for your mirror registry.
imageContentSources section from the output of the command to mirror the repository.