public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-28 05:59:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update _index.md

Browse Source
This commit is contained in:
Denise
2019-11-10 08:32:50 -08:00
committed by GitHub
parent 6d57900705
commit 9c589b6e93
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md
+6 -5
View File
@@ -32,13 +32,14 @@ When provisioning clusters in Rancher using the [vSphere node driver]({{< baseur
![vsphere-node-driver-cloudprovider]({{< baseurl >}}/img/rancher/vsphere-node-driver-cloudprovider.png)
8. Click on **Edit as YAML**
9. Insert the following structure to the pre-populated cluster YAML. In versions prior to v2.3.0, it has to be defined as a top level field. In versions v2.3.0 and higher, it has to be placed under `rancher_kubernetes_engine_config`. Note that the `name` *must* be set to `vsphere`. Refer to the [configuration reference](#configuration-reference) to learn about the properties of the `vsphereCloudProvider` directive.
9. Insert the following structure to the pre-populated cluster YAML. As of Rancher v2.3+, this structure must be placed under `rancher_kubernetes_engine_config`. In versions prior to v2.3, it has to be defined as a top level field. Note that the `name` *must* be set to `vsphere`. Refer to the [configuration reference](#configuration-reference) to learn about the properties of the `vsphereCloudProvider` directive.
```yaml
cloud_provider:
name: vsphere
vsphereCloudProvider:
[Insert provider configuration]
rancher_kubernetes_engine_config: # Required as of Rancher v2.3+
cloud_provider:
name: vsphere
vsphereCloudProvider:
[Insert provider configuration]
```
10. Configure the **Node Pools** per your requirements while ensuring to use a node template that enables disk UUIDs for the VMs (See [Annex - Enable disk UUIDs for vSphere VMs]).