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
Copy file name to clipboardExpand all lines: modules/installation-initializing.adoc
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -326,6 +326,13 @@ After you create the installation configuration file, you can modify the file to
326
326
====
327
327
328
328
... Select the default vCenter datastore to use.
329
+
+
330
+
[WARNING]
331
+
====
332
+
You can specify the path of any datastore that exists in a datastore cluster. By default, Storage Distributed Resource Scheduler (SDRS), which uses Storage vMotion, is automatically enabled for a datastore cluster. Red Hat does not support Storage vMotion, so you must disable Storage DRS to avoid data loss issues for your {product-title} cluster.
333
+
334
+
You cannot specify more than one datastore path. 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".
335
+
====
329
336
... Select the vCenter cluster to install the {product-title} cluster in. The installation program uses the root resource pool of the vSphere cluster as the default resource pool.
330
337
... Select the network in the vCenter instance that contains the virtual IP addresses and DNS records that you configured.
331
338
... Enter the virtual IP address that you configured for control plane API access.
@@ -112,21 +112,29 @@ to increase the performance of your machines' cores. You can disable it by setti
112
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
113
====
114
114
<4> The cluster name that you specified in your DNS records.
115
-
<5> Optional parameter for providing additional configuration for the machine pool parameters for the compute and control plane machines.
115
+
<5> Optional: Provides additional configuration for the machine pool parameters for the compute and control plane machines.
116
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> Optional parameter for providing 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.
118
-
<8> The vSphere disk provisioning method.
117
+
<7> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
118
+
+
119
+
[IMPORTANT]
120
+
====
121
+
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
+
123
+
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
+
====
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.
119
127
ifdef::network[]
120
-
<9> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
128
+
<10> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
121
129
endif::network[]
122
130
ifdef::restricted[]
123
-
<9> The location of the {op-system-first} image that is accessible from the bastion server.
124
-
<10> For `<local_registry>`, specify the registry domain name, and optionally the
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
125
133
port, that your mirror registry uses to serve content. For example
126
134
`registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
127
135
specify the base64-encoded user name and password for your mirror registry.
128
-
<11> Provide the contents of the certificate file that you used for your mirror registry.
129
-
<12> Provide the `imageContentSources` section from the output of the command to mirror the repository.
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.
@@ -153,13 +153,21 @@ value must match the number of control plane machines that you deploy.
153
153
<6> The cluster name that you specified in your DNS records.
154
154
<7> 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.
155
155
<8> The vSphere datacenter.
156
-
<9> Optional parameter. 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`.
157
-
<10> Optional parameter 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 and you do not want to use the default `StorageClass` object, named `thin`, you can omit the `folder` parameter from the `install-config.yaml` file.
158
-
<11> The fully-qualified hostname or IP address of the vCenter server.
156
+
<9> The path to the vSphere datastore that holds virtual machine files, templates, and ISO images.
157
+
+
158
+
[IMPORTANT]
159
+
====
160
+
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.
161
+
162
+
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".
163
+
====
164
+
<10> 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`.
165
+
<11> 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 and you do not want to use the default `StorageClass` object, named `thin`, you can omit the `folder` parameter from the `install-config.yaml` file.
159
166
<12> The password associated with the vSphere user.
160
-
<13> The vSphere disk provisioning method.
167
+
<13> The fully-qualified hostname or IP address of the vCenter server.
168
+
<14> The vSphere disk provisioning method.
161
169
ifndef::openshift-origin[]
162
-
<14> 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.
170
+
<15> 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.
163
171
+
164
172
[IMPORTANT]
165
173
====
@@ -168,13 +176,13 @@ The use of FIPS Validated / Modules in Process cryptographic libraries is only s
168
176
endif::openshift-origin[]
169
177
ifndef::restricted[]
170
178
ifndef::openshift-origin[]
171
-
<15> The pull secret that you obtained from {cluster-manager-url}. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for {product-title} components.
172
-
<16> The public portion of the default SSH key for the `core` user in
179
+
<16> The pull secret that you obtained from {cluster-manager-url}. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for {product-title} components.
180
+
<17> The public portion of the default SSH key for the `core` user in
173
181
{op-system-first}.
174
182
endif::openshift-origin[]
175
183
ifdef::openshift-origin[]
176
-
<15> You obtained the {cluster-manager-url-pull}. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for {product-title} components.
177
-
<16> The public portion of the default SSH key for the `core` user in
184
+
<16> You obtained the {cluster-manager-url-pull}. This pull secret allows you to authenticate with the services that are provided by the included authorities, including Quay.io, which serves the container images for {product-title} components.
185
+
<17> The public portion of the default SSH key for the `core` user in
178
186
{op-system-first}.
179
187
+
180
188
[NOTE]
@@ -185,11 +193,11 @@ endif::openshift-origin[]
185
193
endif::restricted[]
186
194
ifdef::restricted[]
187
195
ifndef::openshift-origin[]
188
-
<15> For `<local_registry>`, specify the registry domain name, and optionally the
196
+
<16> For `<local_registry>`, specify the registry domain name, and optionally the
189
197
port, that your mirror registry uses to serve content. For example
190
198
`registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
191
199
specify the base64-encoded user name and password for your mirror registry.
192
-
<16> The public portion of the default SSH key for the `core` user in
200
+
<17> The public portion of the default SSH key for the `core` user in
193
201
{op-system-first}.
194
202
+
195
203
[NOTE]
@@ -198,11 +206,11 @@ For production {product-title} clusters on which you want to perform installatio
198
206
====
199
207
endif::openshift-origin[]
200
208
ifdef::openshift-origin[]
201
-
<14> For `<local_registry>`, specify the registry domain name, and optionally the
209
+
<15> For `<local_registry>`, specify the registry domain name, and optionally the
202
210
port, that your mirror registry uses to serve content. For example
203
211
`registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
204
212
specify the base64-encoded user name and password for your mirror registry.
205
-
<15> The public portion of the default SSH key for the `core` user in
213
+
<16> The public portion of the default SSH key for the `core` user in
206
214
{op-system-first}.
207
215
+
208
216
[NOTE]
@@ -213,15 +221,15 @@ endif::openshift-origin[]
213
221
endif::restricted[]
214
222
ifdef::restricted[]
215
223
ifndef::openshift-origin[]
216
-
<17> Provide the contents of the certificate file that you used for your mirror
224
+
<18> Provide the contents of the certificate file that you used for your mirror
217
225
registry.
218
-
<18> Provide the `imageContentSources` section from the output of the command to
226
+
<19> Provide the `imageContentSources` section from the output of the command to
219
227
mirror the repository.
220
228
endif::openshift-origin[]
221
229
ifdef::openshift-origin[]
222
-
<16> Provide the contents of the certificate file that you used for your mirror
230
+
<17> Provide the contents of the certificate file that you used for your mirror
223
231
registry.
224
-
<17> Provide the `imageContentSources` section from the output of the command to
232
+
<18> Provide the `imageContentSources` section from the output of the command to
Copy file name to clipboardExpand all lines: modules/installation-vsphere-installer-infra-requirements.adoc
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,6 +393,13 @@ For more information about vMotion and anti-affinity rules, see the VMware vSphe
393
393
--
394
394
* If you are using vSphere volumes in your pods, migrating a VM across datastores either manually or through Storage vMotion causes, invalid references within {product-title} persistent volume (PV) objects. These references prevent affected pods from starting up and can result in data loss.
395
395
* Similarly, {product-title} does not support selective migration of VMDKs across datastores, using datastore clusters for VM provisioning or for dynamic or static provisioning of PVs, or using a datastore that is part of a datastore cluster for dynamic or static provisioning of PVs.
396
+
+
397
+
[IMPORTANT]
398
+
====
399
+
You can specify the path of any datastore that exists in a datastore cluster. By default, Storage Distributed Resource Scheduler (SDRS), which uses Storage vMotion, is automatically enabled for a datastore cluster. Red Hat does not support Storage vMotion, so you must disable Storage DRS to avoid data loss issues for your {product-title} cluster.
400
+
401
+
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".
0 commit comments