github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-12 12:48:51 +00:00
Code Issues Projects Releases Wiki Activity

fixup kubectl walktrough example

Browse Source
This commit is contained in:
Mike Danese
2015-07-16 13:49:31 -07:00
parent 665c951320
commit a654318391
3 changed files with 77 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
docs/user-guide/prereqs.md
View File

@@ -39,10 +39,41 @@ export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
##Configure kubectl
In order for kubectl to find and access the Kubernetes cluster, it needs a [kubeconfig file](kubeconfig-file.md), which is created automatically when creating a cluster using kube-up.sh (see the [getting started guides](../../docs/getting-started-guides/) for more about creating clusters). If you need access to a cluster you didn’t create, see the [Sharing Cluster Access document](sharing-clusters.md).
#### Installing Kubectl
If you downloaded a pre-compiled release, kubectl should be under `platforms/<os>/<arch>`.
If you built from source, kubectl should be either under `_output/local/bin/<os>/<arch>` or `_output/dockerized/bin/<os>/<arch>`.
The kubectl binary doesn't have to be installed to be executable, but the rest of the walkthrough will assume that it's in your PATH.
The simplest way to install is to copy or move kubectl into a dir already in PATH (e.g. `/usr/local/bin`). For example:
```bash
# OS X
sudo cp kubernetes/platforms/darwin/amd64/kubectl /usr/local/bin/kubectl
# Linux
sudo cp kubernetes/platforms/linux/amd64/kubectl /usr/local/bin/kubectl
```
#### Configuring Kubectl
If you used `./cluster/kube-up.sh` to deploy your Kubernetes cluster, kubectl should already be locally configured.
By default, kubectl configuration lives at `~/.kube/config`.
If your cluster was deployed by other means (e.g. a [getting started guide](../getting-started-guides/README.md)) your kubectl client will typically be configured during that process. If for some reason your kubectl client is not yet configured, check out [kubeconfig-file.md](kubeconfig-file.md).
#### Making sure you're ready
Check that kubectl is properly configured by getting the cluster state:
```
```sh
$ kubectl cluster-info
```
If you see a url response, you are ready to go.
## What's next?
[Learn how to launch and expose your application.](quick-start.md)