Ritesh Shukla
parent
e43373ea65
commit
efdc69bdad
|
|
@ -5,19 +5,95 @@ assignees:
|
|||
title: VMware vSphere
|
||||
---
|
||||
|
||||
The example below creates a Kubernetes cluster with 4 worker node Virtual
|
||||
Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This
|
||||
cluster is set up and controlled from your workstation (or wherever you find
|
||||
convenient).
|
||||
This page covers how to get started with deploying Kubernetes on vSphere and details for how to configure the vSphere Cloud Provider.
|
||||
|
||||
* TOC
|
||||
{:toc}
|
||||
|
||||
### Prerequisites
|
||||
### Getting started with vSphere
|
||||
|
||||
1. You need administrator credentials to an ESXi machine or vCenter instance with write mode api access enabled (not available on the free ESXi license).
|
||||
2. You must have Go (see [here](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/development.md#go-versions) for supported versions) installed: [www.golang.org](http://www.golang.org).
|
||||
3. You must have your `GOPATH` set up and include `$GOPATH/bin` in your `PATH`.
|
||||
Kubernetes comes with a cloud provider for vSphere. A quick and easy way to try out the cloud provider is to deploy Kubernetes using [Kubernetes-Anywhere](https://github.com/kubernetes/kubernetes-anywhere).
|
||||
|
||||
This page also describes how to configure and get started with the cloud provider if deploying using custom install scripts.
|
||||
|
||||
### Deploy Kubernetes on vSphere
|
||||
|
||||
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 page](https://github.com/kubernetes/kubernetes-anywhere/blob/master/phase1/vsphere/README.md)
|
||||
|
||||
### vSphere Cloud Provider
|
||||
|
||||
vSphere Cloud Provider allows using vSphere managed storage within Kubernetes. It supports:
|
||||
|
||||
1. Volumes
|
||||
2. Persistent Volumes
|
||||
3. Storage Classes and provisioning of volumes.
|
||||
|
||||
Documentation for how to use vSphere managed storage can be found in the
|
||||
[persistent volumes user
|
||||
guide](http://kubernetes.io/docs/user-guide/persistent-volumes/#vsphere) and the
|
||||
[volumes user
|
||||
guide](http://kubernetes.io/docs/user-guide/volumes/#vspherevolume)
|
||||
|
||||
Examples can be found
|
||||
[here](https://github.com/kubernetes/kubernetes/tree/master/examples/volumes/vsphere)
|
||||
|
||||
#### Configuring vSphere Cloud Provider
|
||||
|
||||
If a Kubernetes cluster has not been deployed using Kubernetes-Anywhere, follow the instructions below to use the vSphere Cloud Provider. These steps are not needed when using Kubernetes-Anywhere, they will be done as part of the deployment.
|
||||
|
||||
* Enable UUID for a VM
|
||||
|
||||
This can be done via [govc tool](https://github.com/vmware/govmomi/tree/master/govc)
|
||||
|
||||
```
|
||||
export GOVC_URL=<IP/URL>
|
||||
export GOVC_USERNAME=<vCenter User>
|
||||
export GOVC_PASSWORD=<vCenter Password>
|
||||
export GOVC_INSECURE=1
|
||||
govc vm.change -e="disk.enableUUID=1" -vm=<VMNAME>
|
||||
```
|
||||
|
||||
* Provide the cloud config file to each instance of kubelet, apiserver and controller manager via ```--cloud-config=<path to file>``` flag. Cloud config [template can be found at Kubernetes-Anywhere] (https://github.com/kubernetes/kubernetes-anywhere/blob/master/phase1/vsphere/vsphere.conf)
|
||||
|
||||
Sample Config:
|
||||
```
|
||||
[Global]
|
||||
user = <User name for vCenter>
|
||||
password = <Password for vCenter>
|
||||
server = <IP/URL for vCenter>
|
||||
port = <Default 443 for vCenter>
|
||||
insecure-flag = <set to 1 if the host above uses a self-signed cert>
|
||||
datacenter = <Datacenter to be used>
|
||||
datastore = <Datastore to use for provisioning volumes using storage classes/dynamic provisioning>
|
||||
working-dir = <Folder in which VMs are provisioned, can be null>
|
||||
[Disk]
|
||||
scsicontrollertype = pvscsi
|
||||
```
|
||||
|
||||
* Set the cloud provider via ```--cloud-provider=vsphere``` flag for each instance of kubelet, apiserver and controller manager.
|
||||
|
||||
|
||||
#### Known issues
|
||||
|
||||
* [Volumes are not removed from a VM configuration if the VM is down](https://github.com/kubernetes/kubernetes/issues/33061). The workaround is to manually remove the disk from VM settings before powering it up.
|
||||
* [FS groups are not supported in 1.4.7](https://github.com/kubernetes/kubernetes/issues/34039)
|
||||
|
||||
### Kube-up (Deprecated)
|
||||
|
||||
Kube-up.sh is no longer supported and is deprecated. The steps for kube-up are included but going forward [kube-anywhere](https://github.com/kubernetes/kubernetes-anywhere) is preferred.
|
||||
|
||||
The recommended version for kube-up is [v1.4.7](https://github.com/kubernetes/kubernetes/releases/tag/v1.4.7)
|
||||
|
||||
The example below creates a Kubernetes cluster with 4 worker node Virtual.
|
||||
Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This cluster is set up and controlled from your workstation (or wherever you find convenient).
|
||||
|
||||
#### Prerequisites
|
||||
|
||||
* You need administrator credentials to an ESXi machine or vCenter instance with write mode api access enabled (not available on the free ESXi license).
|
||||
* You must have Go (see [here](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/development.md#go-versions) for supported versions) installed: [www.golang.org](http://www.golang.org).
|
||||
* You must have your `GOPATH` set up and include `$GOPATH/bin` in your `PATH`.
|
||||
|
||||
```shell
|
||||
export GOPATH=$HOME/src/go
|
||||
|
|
@ -25,7 +101,7 @@ mkdir -p $GOPATH
|
|||
export PATH=$PATH:$GOPATH/bin
|
||||
```
|
||||
|
||||
4. Install the govc tool to interact with ESXi/vCenter. Head to [govc Releases](https://github.com/vmware/govmomi/releases) to download the latest.
|
||||
* Install the govc tool to interact with ESXi/vCenter. Head to [govc Releases](https://github.com/vmware/govmomi/releases) to download the latest.
|
||||
|
||||
```shell
|
||||
# Sample commands for v0.8.0 for 64 bit Linux.
|
||||
|
|
@ -35,9 +111,9 @@ chmod +x govc_linux_amd64
|
|||
mv govc_linux_amd64 /usr/local/bin/govc
|
||||
```
|
||||
|
||||
5. Get or build a [binary release](/docs/getting-started-guides/binary_release)
|
||||
* Get or build a [binary release](/docs/getting-started-guides/binary_release)
|
||||
|
||||
### Setup
|
||||
#### Setup
|
||||
|
||||
Download a prebuilt Debian 8.2 VMDK that we'll use as a base image:
|
||||
|
||||
|
|
@ -91,8 +167,8 @@ Verify that the VMDK was correctly uploaded and expanded to ~3GiB:
|
|||
govc datastore.ls ./kube/
|
||||
```
|
||||
|
||||
If you need to debug any part of the deployment, the guest login for
|
||||
the image that you imported is `kube:kube`. It is normally specified
|
||||
If you need to debug any part of the deployment, the guest login for
|
||||
the image that you imported is `kube:kube`. It is normally specified
|
||||
in the GOVC_GUEST_LOGIN parameter above.
|
||||
|
||||
Also take a look at the file `cluster/vsphere/config-default.sh` and
|
||||
|
|
@ -100,19 +176,19 @@ make any needed changes. You can configure the number of nodes
|
|||
as well as the IP subnets you have made available to Kubernetes, pods,
|
||||
and services.
|
||||
|
||||
### Starting a cluster
|
||||
#### Starting a cluster
|
||||
|
||||
Now, let's continue with deploying Kubernetes.
|
||||
This process takes about ~20-30 minutes depending on your network.
|
||||
|
||||
#### From extracted binary release
|
||||
##### From extracted binary release
|
||||
|
||||
```shell
|
||||
cd kubernetes
|
||||
KUBERNETES_PROVIDER=vsphere cluster/kube-up.sh
|
||||
```
|
||||
|
||||
#### Build from source
|
||||
##### Build from source
|
||||
|
||||
```shell
|
||||
cd kubernetes
|
||||
|
|
@ -126,7 +202,7 @@ deployment works just as any other one!
|
|||
|
||||
**Enjoy!**
|
||||
|
||||
### Extra: debugging deployment failure
|
||||
#### Extra: debugging deployment failure
|
||||
|
||||
The output of `kube-up.sh` displays the IP addresses of the VMs it deploys. You
|
||||
can log into any VM as the `kube` user to poke around and figure out what is
|
||||
|
|
@ -138,7 +214,7 @@ going on (find yourself authorized with your SSH key, or use the password
|
|||
|
||||
IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level
|
||||
-------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ----------------------------
|
||||
Vmware vSphere | Saltstack | Debian | OVS | [docs](/docs/getting-started-guides/vsphere) | | Community ([@imkin](https://github.com/imkin)), ([@abrarshivani](https://github.com/abrarshivani)), ([@kerneltime](https://github.com/kerneltime)), ([@kerneltime](https://github.com/luomiao))
|
||||
Vmware vSphere | Kube-anywhere | Photon OS | Flannel | [docs](/docs/getting-started-guides/vsphere) | | Community ([@abrarshivani](https://github.com/abrarshivani)), ([@kerneltime](https://github.com/kerneltime)), ([@BaluDontu](https://github.com/BaluDontu))([@luomiao](https://github.com/luomiao))
|
||||
|
||||
For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue