github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #1750 from jbeda/vagrant-readme 

Tweak vagrant README a little for new binary deploy world.
pull/6/head
Tim Hockin 2014-10-12 15:01:03 -07:00
parent 695fbee343 5c84cd21a4
commit 5d4e4df390
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/getting-started-guides/vagrant.md
View File

@ -88,13 +88,13 @@ Minion identifier
Alternatively to using the vagrant commands, you can also use the `cluster/kube-*.sh` scripts to interact with the vagrant based provider just like any other hosting platform for kubernetes. Alternatively to using the vagrant commands, you can also use the `cluster/kube-*.sh` scripts to interact with the vagrant based provider just like any other hosting platform for kubernetes.
You need to build the binary required by `kube*` scripts: All of these commands assume you have set `KUBERNETES_PROVIDER` appropriately:
``` ```
hack/build-go.sh export KUBERNETES_PROVIDER=vagrant
``` ```
Then bring up a vagrant cluster Bring up a vagrant cluster
``` ```
cluster/kube-up.sh cluster/kube-up.sh
@ -106,7 +106,7 @@ Destroy the vagrant cluster
cluster/kube-down.sh cluster/kube-down.sh
``` ```
Update the vagrant cluster Update the vagrant cluster after you make changes (only works when building your own releases locally):
``` ```
cluster/kube-push.sh cluster/kube-push.sh