Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tweak vagrant README a little for new binary deploy world. #1750

Merged
merged 1 commit into from
Oct 12, 2014
Merged

Tweak vagrant README a little for new binary deploy world. #1750

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/getting-started-guides/vagrant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

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
Expand All @@ -106,7 +106,7 @@ Destroy the vagrant cluster
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
Expand Down