github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 17:30:00 +00:00
Code Issues Projects Releases Wiki Activity

getting-started gce-guide tells users to use downloaded kubectl

Browse Source
This commit is contained in:
Jeff Lowdermilk 2015-05-12 17:35:57 -07:00
parent 2f2816368f
commit a64cdb34c5
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/getting-started-guides/gce.md
View File

@ -33,16 +33,21 @@ wget -q -O - https://get.k8s.io | bash
This will leave you with a ```kubernetes``` directory on your workstation, and a running cluster. This will leave you with a ```kubernetes``` directory on your workstation, and a running cluster.
Copy the appropriate ```kubectl``` binary to somewhere in your ```PATH```, for example: Add the appropriate binary folder to your ```PATH``` to access kubectl:
```bash ```bash
# OS X # OS X
sudo cp kubernetes/platforms/darwin/amd64/kubectl /usr/local/bin/kubectl export PATH=path/to/kubernetes/platforms/darwin/amd64:$PATH
# Linux # Linux
sudo cp kubernetes/platforms/linux/amd64/kubectl /usr/local/bin/kubectl export PATH=path/to/kubernetes/platforms/linux/amd64:$PATH
``` ```
Note: gcloud also ships with ```kubectl```, which by default is added to your path.
However the gcloud bundled kubectl version may be older than the one downloaded by the
get.k8s.io install script. We recommend you use the downloaded binary to avoid
potential issues with client/server version skew.
If you run into trouble please see the section on [troubleshooting](https://github.com/brendandburns/kubernetes/blob/docs/docs/getting-started-guides/gce.md#troubleshooting), or come ask questions on IRC at #google-containers on freenode. If you run into trouble please see the section on [troubleshooting](https://github.com/brendandburns/kubernetes/blob/docs/docs/getting-started-guides/gce.md#troubleshooting), or come ask questions on IRC at #google-containers on freenode.