From 56922a7da9cf9cd8d31d8f7f004ffc65404367fa Mon Sep 17 00:00:00 2001 From: Richard Larocque Date: Fri, 19 Dec 2014 15:28:15 -0800 Subject: [PATCH] Update the Vagrant getting started guide Fixes two instances that reference the deprecated kubecfg.sh tool. Update the kubernetes_vagrant_auth example to more accurately reflect what happened when I ran the scripts on my local machine. --- docs/getting-started-guides/vagrant.md | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/docs/getting-started-guides/vagrant.md b/docs/getting-started-guides/vagrant.md index 712d2ff0994..fa7e177b9eb 100644 --- a/docs/getting-started-guides/vagrant.md +++ b/docs/getting-started-guides/vagrant.md @@ -74,17 +74,18 @@ To destroy the cluster: vagrant destroy ``` -Once your Vagrant machines are up and provisioned, the first thing to do is to check that you can use the `kubecfg.sh` script. +Once your Vagrant machines are up and provisioned, the first thing to do is to check that you can use the `kubectl.sh` script. You may need to build the binaries first, you can do this with ```make``` ``` -./cluster/kubecfg.sh list /minions -Minion identifier Labels ----------- ---------- -10.245.2.4 -10.245.2.3 -10.245.2.2 +$ ./cluster/kubectl.sh get minions + +NAME LABELS +10.245.1.4 +10.245.1.5 +10.245.1.3 + ``` ### Interacting with your Kubernetes cluster with the `kube-*` scripts. @@ -128,7 +129,11 @@ When using the vagrant provider in Kubernetes, the `cluster/kubectl.sh` script w ``` cat ~/.kubernetes_vagrant_auth { "User": "vagrant", - "Password": "vagrant"} + "Password": "vagrant" + "CAFile": "/home/k8s_user/.kubernetes.vagrant.ca.crt", + "CertFile": "/home/k8s_user/.kubecfg.vagrant.crt", + "KeyFile": "/home/k8s_user/.kubecfg.vagrant.key" +} ``` You should now be set to use the `cluster/kubectl.sh` script. For example try to list the minions that you have started with: