github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-23 11:50:44 +00:00
Code Issues Projects Releases Wiki Activity

Update the Vagrant getting started guide

Browse Source 
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.
This commit is contained in:
Richard Larocque 2014-12-19 15:28:15 -08:00
parent 5038fc0ffa
commit 56922a7da9
1 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 <none>
10.245.2.3 <none>
10.245.2.2 <none>
$ ./cluster/kubectl.sh get minions
NAME LABELS
10.245.1.4 <none>
10.245.1.5 <none>
10.245.1.3 <none>
```
### 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: