You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before you deploy an {product-title} on {{ibm-power-server-name}, you provide parameters to customize your cluster and the platform that hosts it. When you create the `install-config.yaml` file, you provide values for the required parameters through the command line. You can then modify the `install-config.yaml` file to customize your cluster further.
10
+
Before you deploy an {product-title} on {ibm-power-server-name}, you provide parameters to customize your cluster and the platform that hosts it. When you create the `install-config.yaml` file, you provide values for the required parameters through the command line. You can then modify the `install-config.yaml` file to customize your cluster further.
Copy file name to clipboardExpand all lines: modules/installation-configuration-parameters.adoc
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -468,7 +468,7 @@ See _Supported installation methods for different platforms_ in _Installing_ doc
468
468
endif::aws[]
469
469
|String
470
470
endif::openshift-origin[]
471
-
471
+
ifndef::vsphere[]
472
472
|compute:
473
473
hyperthreading:
474
474
|Whether to enable or disable simultaneous multithreading, or `hyperthreading`, on compute machines. By default, simultaneous multithreading is enabled to increase the performance of your machines' cores.
@@ -478,6 +478,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning
478
478
accounts for the dramatically decreased machine performance.
479
479
====
480
480
|`Enabled` or `Disabled`
481
+
endif::vsphere[]
481
482
482
483
|compute:
483
484
name:
@@ -548,6 +549,7 @@ endif::aws[]
548
549
|String
549
550
endif::openshift-origin[]
550
551
552
+
ifndef::vsphere[]
551
553
|controlPlane:
552
554
hyperthreading:
553
555
|Whether to enable or disable simultaneous multithreading, or `hyperthreading`, on control plane machines. By default, simultaneous multithreading is enabled to increase the performance of your machines' cores.
@@ -557,6 +559,7 @@ If you disable simultaneous multithreading, ensure that your capacity planning
557
559
accounts for the dramatically decreased machine performance.
558
560
====
559
561
|`Enabled` or `Disabled`
562
+
endif::vsphere[]
560
563
561
564
|controlPlane:
562
565
name:
@@ -710,27 +713,29 @@ endif::ibm-power-vs[]
710
713
[.small]
711
714
--
712
715
1. Not all CCO modes are supported for all cloud providers. For more information about CCO modes, see the "Managing cloud provider credentials" entry in the _Authentication and authorization_ content.
713
-
+
714
716
ifdef::aws,gcp[]
717
+
+
715
718
[NOTE]
716
719
====
717
720
ifdef::aws[If your AWS account has service control policies (SCP) enabled, you must configure the `credentialsMode` parameter to `Mint`, `Passthrough`, or `Manual`.]
718
721
ifdef::gcp[If you are installing on GCP into a shared virtual private cloud (VPC), `credentialsMode` must be set to `Passthrough` or `Manual`.]
719
722
====
720
-
+
721
723
endif::aws,gcp[]
724
+
ifdef::aws,gcp,azure[]
725
+
+
722
726
[IMPORTANT]
723
727
====
724
-
ifdef::aws,gcp,azure[Setting this parameter to `Manual` enables alternatives to storing administrator-level secrets in the `kube-system` project, which require additional configuration steps. For more information, see "Alternatives to storing administrator-level secrets in the kube-system project".]
728
+
Setting this parameter to `Manual` enables alternatives to storing administrator-level secrets in the `kube-system` project, which require additional configuration steps. For more information, see "Alternatives to storing administrator-level secrets in the kube-system project".
725
729
====
726
-
--
727
-
730
+
endif::aws,gcp,azure[]
728
731
ifdef::ibm-power-vs[]
732
+
+
729
733
[NOTE]
730
734
====
731
735
Cloud connections are no longer supported in the `install-config.yaml` while deploying in the `dal10` region, as they have been replaced by the Power Edge Router (PER).
<1> The base domain of the cluster. All DNS records must be sub-domains of this base and include the cluster name.
106
104
<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. Only one control plane pool is used.
107
-
<3> Whether to enable or disable simultaneous multithreading, or `hyperthreading`. By default, simultaneous multithreading is enabled
108
-
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.
109
-
+
110
-
[IMPORTANT]
111
-
====
112
-
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.
113
-
====
114
-
<4> The cluster name that you specified in your DNS records.
115
-
<5> Optional: Provides additional configuration for the machine pool parameters for the compute and control plane machines.
116
-
<6> Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a `datastore` object. A failure domain defines the vCenter location for {product-title} cluster nodes.
117
-
<7> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
105
+
<3> The cluster name that you specified in your DNS records.
106
+
<4> Optional: Provides additional configuration for the machine pool parameters for the compute and control plane machines.
107
+
<5> Establishes the relationships between a region and zone. You define a failure domain by using vCenter objects, such as a `datastore` object. A failure domain defines the vCenter location for {product-title} cluster nodes.
108
+
<6> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
118
109
+
119
110
[IMPORTANT]
120
111
====
121
112
You can specify the path of any datastore that exists in a datastore cluster. By default, Storage vMotion is automatically enabled for a datastore cluster. Red Hat does not support Storage vMotion, so you must disable Storage vMotion to avoid data loss issues for your {product-title} cluster.
122
113
123
114
If you must specify VMs across multiple datastores, use a `datastore` object to specify a failure domain in your cluster's `install-config.yaml` configuration file. For more information, see "VMware vSphere region and zone enablement".
124
115
====
125
-
<8> Optional: Provides an existing resource pool for machine creation. If you do not specify a value, the installation program uses the root resource pool of the vSphere cluster.
126
-
<9> The vSphere disk provisioning method.
116
+
<7> Optional: Provides an existing resource pool for machine creation. If you do not specify a value, the installation program uses the root resource pool of the vSphere cluster.
117
+
<8> The vSphere disk provisioning method.
127
118
ifdef::network[]
128
-
<10> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
119
+
<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
129
120
endif::network[]
130
121
ifdef::restricted[]
131
-
<10> The location of the {op-system-first} image that is accessible from the bastion server.
132
-
<11> For `<local_registry>`, specify the registry domain name, and optionally the
122
+
<9> The location of the {op-system-first} image that is accessible from the bastion server.
123
+
<10> For `<local_registry>`, specify the registry domain name, and optionally the
133
124
port, that your mirror registry uses to serve content. For example
134
125
`registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
135
126
specify the base64-encoded user name and password for your mirror registry.
136
-
<12> Provide the contents of the certificate file that you used for your mirror registry.
137
-
<13> Provide the `imageContentSources` section from the output of the command to mirror the repository.
127
+
<11> Provide the contents of the certificate file that you used for your mirror registry.
128
+
<12> Provide the `imageContentSources` section from the output of the command to mirror the repository.
ifndef::ibm-z,ibm-power,ibm-cloud-vpc[|{op-system}, {op-system-base} 8.6, {op-system-base} 8.7, or {op-system-base} 8.8 ^[3]^]
187
+
ifndef::ibm-z,ibm-power,ibm-cloud-vpc,vsphere[|{op-system}, {op-system-base} 8.6, {op-system-base} 8.7, or {op-system-base} 8.8 ^[3]^]
188
+
ifdef::vsphere[|{op-system}, {op-system-base} 8.6, {op-system-base} 8.7, or {op-system-base} 8.8 ^[2]^]
176
189
|2
177
190
|8 GB
178
191
|100 GB
@@ -206,16 +219,20 @@ endif::ibm-z[]
206
219
ifdef::bare-metal[]
207
220
1. One CPU is equivalent to one physical core when simultaneous multithreading (SMT), or hyperthreading, is not enabled. When enabled, use the following formula to calculate the corresponding ratio: (threads per core × cores) × sockets = CPUs.
208
221
endif::bare-metal[]
209
-
ifndef::ibm-z,bare-metal,ibm-cloud-vpc[]
222
+
ifndef::ibm-z,bare-metal,ibm-cloud-vpc,vsphere[]
210
223
1. One vCPU is equivalent to one physical core when simultaneous multithreading (SMT), or hyperthreading, is not enabled. When enabled, use the following formula to calculate the corresponding ratio: (threads per core × cores) × sockets = vCPUs.
211
-
endif::ibm-z,bare-metal,ibm-cloud-vpc[]
212
-
ifndef::ibm-z,ibm-power,ibm-cloud-vpc[]
224
+
endif::ibm-z,bare-metal,ibm-cloud-vpc,vsphere[]
225
+
ifndef::ibm-z,ibm-power,ibm-cloud-vpc,vsphere[]
213
226
2. {product-title} and Kubernetes are sensitive to disk performance, and faster storage is recommended, particularly for etcd on the control plane nodes which require a 10 ms p99 fsync duration. Note that on many cloud platforms, storage size and IOPS scale together, so you might need to over-allocate storage volume to obtain sufficient performance.
214
227
3. As with all user-provisioned installations, if you choose to use {op-system-base} compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of {op-system-base} 7 compute machines is deprecated and has been removed in {product-title} 4.10 and later.
215
-
endif::ibm-z,ibm-power,ibm-cloud-vpc[]
228
+
endif::ibm-z,ibm-power,ibm-cloud-vpc,vsphere[]
216
229
ifdef::ibm-power[]
217
230
2. {product-title} and Kubernetes are sensitive to disk performance, and faster storage is recommended, particularly for etcd on the control plane nodes. Note that on many cloud platforms, storage size and IOPS scale together, so you might need to over-allocate storage volume to obtain sufficient performance.
218
231
endif::ibm-power[]
232
+
ifdef::vsphere[]
233
+
1. {product-title} and Kubernetes are sensitive to disk performance, and faster storage is recommended, particularly for etcd on the control plane nodes which require a 10 ms p99 fsync duration. Note that on many cloud platforms, storage size and IOPS scale together, so you might need to over-allocate storage volume to obtain sufficient performance.
234
+
2. As with all user-provisioned installations, if you choose to use {op-system-base} compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of {op-system-base} 7 compute machines is deprecated and has been removed in {product-title} 4.10 and later.
0 commit comments