From 6d57900705f24587242580e094a4622ea14892c7 Mon Sep 17 00:00:00 2001 From: Alena Prokharchyk Date: Thu, 10 Oct 2019 16:22:06 -0700 Subject: [PATCH 1/2] Fix for cloud provider section in cluster.yml for vSphere --- .../latest/en/config-options/cloud-providers/vsphere/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md b/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md index f517fe2d20d..88a70c231fc 100644 --- a/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md +++ b/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md @@ -32,7 +32,7 @@ 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 top-level structure to the pre-populated cluster YAML. 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. 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. ```yaml cloud_provider: From 9c589b6e939a36f35972c086932a4d791f6760d3 Mon Sep 17 00:00:00 2001 From: Denise Date: Sun, 10 Nov 2019 08:32:50 -0800 Subject: [PATCH 2/2] Update _index.md --- .../config-options/cloud-providers/vsphere/_index.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md b/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md index 88a70c231fc..bc1ac20712d 100644 --- a/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md +++ b/content/rke/latest/en/config-options/cloud-providers/vsphere/_index.md @@ -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]).