Update vsphere.md to include guest login info

This seems to be an afterthought. Merging into main docs.
pull/1007/head
Kyle Gordon 2016-08-10 10:39:47 +01:00 committed by GitHub
parent 6661049014
commit 75feea16b4
1 changed files with 4 additions and 3 deletions

View File

@ -53,6 +53,7 @@ export GOVC_NETWORK='Network Name' # Name of the network the vms should join. Ma
export GOVC_INSECURE=1 # If the host above uses a self-signed cert export GOVC_INSECURE=1 # If the host above uses a self-signed cert
export GOVC_DATASTORE='target datastore' export GOVC_DATASTORE='target datastore'
export GOVC_RESOURCE_POOL='resource pool or cluster with access to datastore' export GOVC_RESOURCE_POOL='resource pool or cluster with access to datastore'
export GOVC_GUEST_LOGIN=kube:kube # Used for logging into kube.vmdk during deployment.
govc import.vmdk kube.vmdk ./kube/ govc import.vmdk kube.vmdk ./kube/
``` ```
@ -62,9 +63,9 @@ Verify that the VMDK was correctly uploaded and expanded to ~3GiB:
```shell ```shell
govc datastore.ls ./kube/ govc datastore.ls ./kube/
``` ```
If you need to debug any part of the deployment, the guest login for
Take a look at the file `cluster/vsphere/config-common.sh` fill in the required the image that you imported is `kube:kube`. It is normally specified
parameters. The guest login for the image that you imported is `kube:kube`. in the GOVC_GUEST_LOGIN parameter above.
Also take a look at the file `cluster/vsphere/config-default.sh` and Also take a look at the file `cluster/vsphere/config-default.sh` and
make any needed changes. You can configure the number of nodes make any needed changes. You can configure the number of nodes