1 |
The base domain of the cluster. All DNS records must be sub-domains of this
base and include the cluster name. |
2 |
The 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. Although both sections
currently define a single machine pool, it is possible that future versions
of OKD will support defining multiple compute pools during
installation. Only one control plane pool is used. |
3 |
Whether to enable or disable simultaneous multithreading, or
hyperthreading . By default, simultaneous multithreading is enabled
to increase the performance of your machines' cores. You can disable it by
setting the parameter value to Disabled . If you disable simultaneous
multithreading in some cluster machines, you must disable it in all cluster
machines.
|
If you disable simultaneous multithreading, ensure that your capacity planning
accounts for the dramatically decreased machine performance.
Your machines must use at least 8 CPUs and 32 GB of RAM if you disable
simultaneous multithreading.
|
|
4 |
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 OKD. |
5 |
The number of control plane machines that you add to the cluster. Because
the cluster uses this values as the number of etcd endpoints in the cluster, the
value must match the number of control plane machines that you deploy. |
6 |
The cluster name that you specified in your DNS records. |
7 |
The fully-qualified hostname or IP address of the vCenter server. |
8 |
The name of the user for accessing the server. This user must have at least
the roles and privileges that are required for
static or dynamic persistent volume provisioning
in vSphere. |
9 |
The password associated with the vSphere user. |
10 |
The vSphere datacenter. |
11 |
The default vSphere datastore to use. |
12 |
Optional: For installer-provisioned infrastructure, the absolute path of an existing folder where the installation program creates the virtual machines, for example, /<datacenter_name>/vm/<folder_name>/<subfolder_name> . If you do not provide this value, the installation program creates a top-level folder in the datacenter virtual machine folder that is named with the infrastructure ID. If you are providing the infrastructure for the cluster, omit this parameter. |
13 |
Optional: For installer-provisioned infrastructure, the absolute path of an existing resource pool where the installation program creates the virtual machines, for example, /<datacenter_name>/host/<cluster_name>/Resources/<resource_pool_name>/<optional_nested_resource_pool_name> . If you do not specify a value, resources are installed in the root of the cluster /example_datacenter/host/example_cluster/Resources . |
14 |
The vSphere disk provisioning method. |
15 |
For <local_registry> , specify the registry domain name, and optionally the
port, that your mirror registry uses to serve content. For example
registry.example.com or registry.example.com:5000 . For <credentials> ,
specify the base64-encoded user name and password for your mirror registry. |
16 |
The public portion of the default SSH key for the core user in
Fedora CoreOS (FCOS).
|
For production OKD clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your ssh-agent process uses.
|
|
17 |
Provide the contents of the certificate file that you used for your mirror
registry. |
18 |
Provide the imageContentSources section from the output of the command to
mirror the repository. |