From e6964cdedcbf9f4cb05c6ef1cedb2b69ad32b043 Mon Sep 17 00:00:00 2001 From: Mark Janssen Date: Wed, 17 Jan 2018 21:48:24 +0100 Subject: [PATCH] Fix vSphere getting started guide for Kubernetes 1.9 --- docs/getting-started-guides/vsphere.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-guides/vsphere.md b/docs/getting-started-guides/vsphere.md index afdaa860c7..f683f0b79f 100644 --- a/docs/getting-started-guides/vsphere.md +++ b/docs/getting-started-guides/vsphere.md @@ -117,7 +117,7 @@ vSphere Cloud Provider requires the following minimal set of privileges to inter This config file needs to be placed in the shared directory which should be accessible from kubelet container, controller-manager pod, and API server pod. -**```vsphere.conf``` for Master Node:** +**`vsphere.conf` for master node:** ``` [Global] @@ -137,7 +137,9 @@ This config file needs to be placed in the shared directory which should be acce Note: **```vm-name``` parameter is introduced in 1.6.4 release.** Both ```vm-uuid``` and ```vm-name``` are optional parameters. If ```vm-name``` is specified then ```vm-uuid``` is not used. If both are not specified then kubelet will get vm-uuid from `/sys/class/dmi/id/product_serial` and query vCenter to find the Node VM's name. -**```vsphere.conf``` for Worker Nodes:** (Only Applicable to 1.6.4 release and above. For older releases this file should have all the parameters specified in Master node's ```vSphere.conf``` file). +**`vsphere.conf` for worker nodes:** + +Applicable only to versions 1.6.4 to 1.8.x. For versions earlier than 1.6.4, this file should have all the parameters specified in the master node's `vsphere.conf` file. In version 1.9.0 and later, the worker nodes do not need a cloud config file. ``` [Global]