summaryrefslogtreecommitdiff
path: root/developer-guides
diff options
context:
space:
mode:
authorDaniel Smith <dbsmith@google.com>2015-07-16 19:01:02 -0700
committerDaniel Smith <dbsmith@google.com>2015-07-17 11:04:46 -0700
commit35f2829ae014c08b847b59ce06a205cc3fbb8770 (patch)
treec201d2c3b0879a1311d12525642c9733651ecd87 /developer-guides
parent6a198dfa61ce281f5d092a9c2576c46bb01a1482 (diff)
apply changes
Diffstat (limited to 'developer-guides')
-rw-r--r--developer-guides/vagrant.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/developer-guides/vagrant.md b/developer-guides/vagrant.md
index 5b4013e3..2b6fcc42 100644
--- a/developer-guides/vagrant.md
+++ b/developer-guides/vagrant.md
@@ -83,6 +83,7 @@ vagrant ssh minion-3
```
To view the service status and/or logs on the kubernetes-master:
+
```sh
vagrant ssh master
[vagrant@kubernetes-master ~] $ sudo systemctl status kube-apiserver
@@ -96,6 +97,7 @@ vagrant ssh master
```
To view the services on any of the nodes:
+
```sh
vagrant ssh minion-1
[vagrant@kubernetes-minion-1] $ sudo systemctl status docker
@@ -109,17 +111,20 @@ vagrant ssh minion-1
With your Kubernetes cluster up, you can manage the nodes in your cluster with the regular Vagrant commands.
To push updates to new Kubernetes code after making source changes:
+
```sh
./cluster/kube-push.sh
```
To stop and then restart the cluster:
+
```sh
vagrant halt
./cluster/kube-up.sh
```
To destroy the cluster:
+
```sh
vagrant destroy
```