Fix typos
docs/admin/kube-apiserver.md, Line112: "recieving" --> "receiving" docs/getting-started-guides/vsphere.md: add "." and "does" --> "do"
This commit is contained in:
linweibin
@@ -20,7 +20,7 @@ This page also describes how to configure and get started with the cloud provide
|
||||
|
||||
To start using Kubernetes on top of vSphere and use the vSphere Cloud Provider use Kubernetes-Anywhere. Kubernetes-Anywhere will deploy and configure a cluster from scratch.
|
||||
|
||||
Detailed steps can be found at the [getting started with Kubernetes-Anywhere on vSphere](https://git.k8s.io/kubernetes-anywhere/phase1/vsphere/README.md) page
|
||||
Detailed steps can be found at the [getting started with Kubernetes-Anywhere on vSphere](https://git.k8s.io/kubernetes-anywhere/phase1/vsphere/README.md) page.
|
||||
|
||||
### vSphere Cloud Provider
|
||||
|
||||
@@ -31,9 +31,9 @@ vSphere Cloud Provider allows using vSphere managed storage within Kubernetes. I
|
||||
3. Storage Classes and provisioning of volumes.
|
||||
4. vSphere Storage Policy Based Management for Containers orchestrated by Kubernetes.
|
||||
|
||||
Documentation for how to use vSphere managed storage can be found in the [persistent volumes user guide](/docs/concepts/storage/persistent-volumes/#vsphere) and the [volumes user guide](/docs/concepts/storage/volumes/#vspherevolume)
|
||||
Documentation for how to use vSphere managed storage can be found in the [persistent volumes user guide](/docs/concepts/storage/persistent-volumes/#vsphere) and the [volumes user guide](/docs/concepts/storage/volumes/#vspherevolume).
|
||||
|
||||
Examples can be found [here](https://git.k8s.io/kubernetes/examples/volumes/vsphere)
|
||||
Examples can be found [here](https://git.k8s.io/kubernetes/examples/volumes/vsphere).
|
||||
|
||||
#### Enable vSphere Cloud Provider
|
||||
|
||||
@@ -41,15 +41,15 @@ If a Kubernetes cluster has not been deployed using Kubernetes-Anywhere, follow
|
||||
|
||||
**Step-1** [Create a VM folder](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vcenterhost.doc/GUID-031BDB12-D3B2-4E2D-80E6-604F304B4D0C.html) and move Kubernetes Node VMs to this folder.
|
||||
|
||||
**Step-2** Make sure Node VM names must comply with the regex `[a-z](([-0-9a-z]+)?[0-9a-z])?(\.[a-z0-9](([-0-9a-z]+)?[0-9a-z])?)*` If Node VMs does not comply with this regex, rename them and make it compliant to this regex.
|
||||
**Step-2** Make sure Node VM names must comply with the regex `[a-z](([-0-9a-z]+)?[0-9a-z])?(\.[a-z0-9](([-0-9a-z]+)?[0-9a-z])?)*`. If Node VMs do not comply with this regex, rename them and make it compliant to this regex.
|
||||
|
||||
Node VM names constraints:
|
||||
|
||||
* VM names can not begin with numbers.
|
||||
* VM names can not have capital letters, any special characters except `.` and `-`.
|
||||
* VM names can not be shorter than 3 chars and longer than 63
|
||||
* VM names can not be shorter than 3 chars and longer than 63.
|
||||
|
||||
**Step-3** Enable disk UUID on Node virtual machines
|
||||
**Step-3** Enable disk UUID on Node virtual machines.
|
||||
|
||||
The disk.EnableUUID parameter must be set to "TRUE" for each Node VM. This step is necessary so that the VMDK always presents a consistent UUID to the VM, thus allowing the disk to be mounted properly.
|
||||
|
||||
@@ -114,7 +114,7 @@ vSphere Cloud Provider requires the following minimal set of privileges to inter
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Step-5** Create the vSphere cloud config file (`vsphere.conf`). Cloud config template can be found [here](https://github.com/kubernetes/kubernetes-anywhere/blob/master/phase1/vsphere/vsphere.conf)
|
||||
**Step-5** Create the vSphere cloud config file (`vsphere.conf`). Cloud config template can be found [here](https://github.com/kubernetes/kubernetes-anywhere/blob/master/phase1/vsphere/vsphere.conf).
|
||||
|
||||
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.
|
||||
|
||||
@@ -138,7 +138,7 @@ 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:** (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).
|
||||
|
||||
```
|
||||
[Global]
|
||||
@@ -184,7 +184,7 @@ Below is summary of supported parameters in the `vsphere.conf` file
|
||||
--cloud-config=<Path of the vsphere.conf file>
|
||||
```
|
||||
|
||||
Manifest files for API server and controller-manager are generally located at `/etc/kubernetes`
|
||||
Manifest files for API server and controller-manager are generally located at `/etc/kubernetes`.
|
||||
|
||||
**Step-7** Restart Kubelet on all nodes.
|
||||
* Reload kubelet systemd unit file using ```systemctl daemon-reload```
|
||||
|
||||
Reference in New Issue
Block a user