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-configuration-parameters.adoc
+56Lines changed: 56 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1831,6 +1831,62 @@ Additional Nutanix configuration parameters are described in the following table
1831
1831
|====
1832
1832
|Parameter|Description|Values
1833
1833
1834
+
|`compute.platform.nutanix.categories.key`
1835
+
|The name of a prism category key to apply to compute VMs. This parameter must be accompanied by the `value` parameter, and both `key` and `value` parameters must exist in Prism Central. For more information on categories, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_6:ssp-ssp-categories-manage-pc-c.html[Category management].
1836
+
|String
1837
+
1838
+
|`compute.platform.nutanix.categories.value`
1839
+
|The value of a prism category key-value pair to apply to compute VMs. This parameter must be accompanied by the `key` parameter, and both `key` and `value` parameters must exist in Prism Central.
1840
+
|String
1841
+
1842
+
|`compute.platform.nutanix.project.type`
1843
+
|The type of identifier you use to select a project for compute VMs. Projects define logical groups of user roles for managing permissions, networks, and other parameters. For more information on projects, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_9:ssp-app-mgmt-project-env-c.html[Projects Overview].
1844
+
|`name` or `uuid`
1845
+
1846
+
|`compute.platform.nutanix.project.name` or `compute.platform.nutanix.project.uuid`
1847
+
|The name or UUID of a project with which compute VMs are associated. This parameter must be accompanied by the `type` parameter.
1848
+
|String
1849
+
1850
+
|`compute.platform.nutanix.bootType`
1851
+
|The boot type that the compute machines use. You must use the `Legacy` boot type in {product-title} {product-version}. For more information on boot types, see link:https://portal.nutanix.com/page/documents/kbs/details?targetId=kA07V000000H3K9SAK[Understanding UEFI, Secure Boot, and TPM in the Virtualized Environment].
1852
+
|`Legacy`, `SecureBoot` or `UEFI`. The default is `Legacy`.
1853
+
1854
+
|`controlPlane.platform.nutanix.categories.key`
1855
+
|The name of a prism category key to apply to control plane VMs. This parameter must be accompanied by the `value` parameter, and both `key` and `value` parameters must exist in Prism Central. For more information on categories, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_6:ssp-ssp-categories-manage-pc-c.html[Category management].
1856
+
|String
1857
+
1858
+
|`controlPlane.platform.nutanix.categories.value`
1859
+
|The value of a prism category key-value pair to apply to control plane VMs. This parameter must be accompanied by the `key` parameter, and both `key` and `value` parameters must exist in Prism Central.
1860
+
|String
1861
+
1862
+
|`controlPlane.platform.nutanix.project.type`
1863
+
|The type of identifier you use to select a project for control plane VMs. Projects define logical groups of user roles for managing permissions, networks, and other parameters. For more information on projects, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_9:ssp-app-mgmt-project-env-c.html[Projects Overview].
1864
+
|`name` or `uuid`
1865
+
1866
+
|`controlPlane.platform.nutanix.project.name` or `controlPlane.platform.nutanix.project.uuid`
1867
+
|The name or UUID of a project with which control plane VMs are associated. This parameter must be accompanied by the `type` parameter.
|The name of a prism category key to apply to all VMs. This parameter must be accompanied by the `value` parameter, and both `key` and `value` parameters must exist in Prism Central. For more information on categories, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_6:ssp-ssp-categories-manage-pc-c.html[Category management].
|The value of a prism category key-value pair to apply to all VMs. This parameter must be accompanied by the `key` parameter, and both `key` and `value` parameters must exist in Prism Central.
|The type of identifier you use to select a project for all VMs. Projects define logical groups of user roles for managing permissions, networks, and other parameters. For more information on projects, see link:https://portal.nutanix.com/page/documents/details?targetId=Prism-Central-Guide-vpc_2022_9:ssp-app-mgmt-project-env-c.html[Projects Overview].
1880
+
|`name` or `uuid`.
1881
+
1882
+
|`platform.nutanix.defaultMachinePlatform.project.name` or `platform.nutanix.defaultMachinePlatform.project.uuid`
1883
+
|The name or UUID of a project with which all VMs are associated. This parameter must be accompanied by the `type` parameter.
|The boot type for all machines. You must use the `Legacy` boot type in {product-title} {product-version}. For more information on boot types, see link:https://portal.nutanix.com/page/documents/kbs/details?targetId=kA07V000000H3K9SAK[Understanding UEFI, Secure Boot, and TPM in the Virtualized Environment].
1888
+
|`Legacy`, `SecureBoot` or `UEFI`. The default is `Legacy`.
1889
+
1834
1890
|`platform.nutanix.apiVIP`
1835
1891
|The virtual IP (VIP) address that you configured for control plane API access.
<1> Required. The installation program prompts you for this value.
@@ -98,20 +112,22 @@ endif::openshift-origin[]
98
112
If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance.
99
113
====
100
114
<4> Optional: Provide additional configuration for the machine pool parameters for the compute and control plane machines.
101
-
<5> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
115
+
<5> Optional: Provide one or more pairs of a prism category key and a prism category value. These category key-value pairs must exist in Prism Central. You can provide separate categories to compute machines, control plane machines, or all machines.
116
+
<6> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
102
117
ifndef::openshift-origin[]
103
-
<6> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server and pointing the installation program to the image.
104
-
<7> 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.
118
+
<7> Optional: Specify a project with which VMs are associated. Specify either `name` or `uuid` for the project type, and then provide the corresponding UUID or project name. You can associate projects to compute machines, control plane machines, or all machines.
119
+
<8> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server and pointing the installation program to the image.
120
+
<9> 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.
105
121
+
106
122
[IMPORTANT]
107
123
====
108
124
The use of FIPS Validated or Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
109
125
====
110
-
<8> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
126
+
<10> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
111
127
endif::openshift-origin[]
112
128
ifdef::openshift-origin[]
113
-
<6> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server and pointing the installation program to the image.
114
-
<7> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
129
+
<7> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server and pointing the installation program to the image.
130
+
<8> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
If you disable simultaneous multithreading, ensure that your capacity planning accounts for the dramatically decreased machine performance.
224
254
====
225
255
<4> Optional: Provide additional configuration for the machine pool parameters for the compute and control plane machines.
226
-
<5> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
227
-
<6> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server or Nutanix Objects and pointing the installation program to the image.
228
-
<7> 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>`,
256
+
<5> Optional: Provide one or more pairs of a prism category key and a prism category value. These category key-value pairs must exist in Prism Central. You can provide separate categories to compute machines, control plane machines, or all machines.
257
+
<6> The cluster network plugin to install. The supported values are `OVNKubernetes` and `OpenShiftSDN`. The default value is `OVNKubernetes`.
258
+
<7> Optional: Specify a project with which VMs are associated. Specify either `name` or `uuid` for the project type, and then provide the corresponding UUID or project name. You can associate projects to compute machines, control plane machines, or all machines.
259
+
<8> Optional: By default, the installation program downloads and installs the {op-system-first} image. If Prism Central does not have internet access, you can override the default behavior by hosting the {op-system} image on any HTTP server or Nutanix Objects and pointing the installation program to the image.
260
+
<9> 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>`,
229
261
specify the base64-encoded user name and password for your mirror registry.
230
262
ifndef::openshift-origin[]
231
-
<8> 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.
263
+
<10> 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.
232
264
+
233
265
[IMPORTANT]
234
266
====
235
267
The use of FIPS Validated or Modules in Process cryptographic libraries is only supported on {product-title} deployments on the `x86_64` architecture.
236
268
====
237
-
<9> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
269
+
<11> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
238
270
+
239
271
[NOTE]
240
272
====
241
273
For production {product-title} clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your `ssh-agent` process uses.
242
274
====
243
275
endif::openshift-origin[]
244
276
ifdef::openshift-origin[]
245
-
<8> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
277
+
<10> Optional: You can provide the `sshKey` value that you use to access the machines in your cluster.
246
278
+
247
279
[NOTE]
248
280
====
249
281
For production {product-title} clusters on which you want to perform installation debugging or disaster recovery, specify an SSH key that your `ssh-agent` process uses.
250
282
====
251
283
endif::openshift-origin[]
252
284
ifndef::openshift-origin[]
253
-
<10> Provide the contents of the certificate file that you used for your mirror registry.
254
-
<11> Provide these values from the `metadata.name: release-0` section of the `imageContentSourcePolicy.yaml` file that was created when you mirrored the registry.
285
+
<12> Provide the contents of the certificate file that you used for your mirror registry.
286
+
<13> Provide these values from the `metadata.name: release-0` section of the `imageContentSourcePolicy.yaml` file that was created when you mirrored the registry.
255
287
endif::openshift-origin[]
256
288
ifdef::openshift-origin[]
257
-
<9> Provide the contents of the certificate file that you used for your mirror registry.
258
-
<10> Provide these values from the `metadata.name: release-0` section of the `imageContentSourcePolicy.yaml` file that was created when you mirrored the registry.
289
+
<11> Provide the contents of the certificate file that you used for your mirror registry.
290
+
<12> Provide these values from the `metadata.name: release-0` section of the `imageContentSourcePolicy.yaml` file that was created when you mirrored the registry.
0 commit comments