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
@@ -114,18 +116,20 @@ You can specify the path of any datastore that exists in a datastore cluster. By
114
116
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".
115
117
====
116
118
<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.
119
+
<8> Optional: Each VM created by {product-title} is assigned a unique tag that is specific to the cluster. The assigned tag enables the installation program to identify and remove the associated VMs when a cluster is decommissioned. You can list up to ten additional tag IDs to be attached to the VMs provisioned by the installation program.
120
+
<9> The ID of the tag to be associated by the installation program. For example, `urn:vmomi:InventoryServiceTag:208e713c-cae3-4b7f-918e-4051ca7d1f97:GLOBAL`. For more information about determining the tag ID, see the link:https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-E8E854DD-AA97-4E0C-8419-CE84F93C4058.html[vSphere Tags and Attributes documentation].
121
+
<10> The vSphere disk provisioning method.
118
122
ifdef::network[]
119
-
<9> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
123
+
<11> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
120
124
endif::network[]
121
125
ifdef::restricted[]
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
126
+
<11> The location of the {op-system-first} image that is accessible from the bastion server.
127
+
<12> For `<local_registry>`, specify the registry domain name, and optionally the
124
128
port, that your mirror registry uses to serve content. For example
125
129
`registry.example.com` or `registry.example.com:5000`. For `<credentials>`,
126
130
specify the base64-encoded user name and password for your mirror registry.
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.
131
+
<13> Provide the contents of the certificate file that you used for your mirror registry.
132
+
<14> Provide the `imageContentSources` section from the output of the command to mirror the repository.
0 commit comments