Merge pull request #6998 from praseodym/fix-vsphere-docs-for-1.9
Fix vSphere getting started guide for Kubernetes 1.9pull/6538/merge
commit
03f4a117bd
|
@ -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]
|
||||
|
|
Loading…
Reference in New Issue