Combine install and build instructions

Previously this information was scattered in multiple places, combine
this into one location.
This commit is contained in:
Ashley Penney 2017-01-30 14:53:01 -05:00
parent 5c960e15fc
commit 2a77022948
2 changed files with 29 additions and 27 deletions

View File

@ -2,38 +2,15 @@
<img src="img/k8s-aws.png"> </image> <img src="img/k8s-aws.png"> </image>
</p> </p>
# Getting Started # Getting Started
## Install kops ## Install kops
From Homebrew: Before we can bring up the cluster we need to [install the CLI tool](install.md) `kops`.
```bash
brew update && brew install --HEAD kops
```
From Source:
```bash
go get -d k8s.io/kops
cd ${GOPATH}/src/k8s.io/kops/
git checkout release
make
```
See our [installation guide](build.md) for more information
## Install kubectl ## Install kubectl
It is a good idea to grab a fresh copy of `kubectl` now if you don't already have it. In order to control Kubernetes clusters we need to [install the CLI tool](install.md) `kubectl`.
#### OS X
```
brew install kubernetes-cli
```
#### Other Platforms #### Other Platforms

View File

@ -1,4 +1,30 @@
# Building from source # Installing Kops (Binaries)
## Darwin (MacOS)
From Homebrew:
```bash
brew update && brew install --HEAD kops
```
# Installing Kubectl
`kubectl` is the CLI tool to manage and operate Kubernetes clusters. You can install it as follows.
## Darwin (MacOS)
```
brew install kubernetes-cli
```
## Other Platforms
* [Kubernetes Latest Release](https://github.com/kubernetes/kubernetes/releases/latest)
* [Installation Guide](http://kubernetes.io/docs/user-guide/prereqs/)
# Installing Kops (Source)
``` ```
go get -d k8s.io/kops go get -d k8s.io/kops
@ -10,7 +36,6 @@ make
* The `release` branch is where releases are taken from. This is the stable code branch. * The `release` branch is where releases are taken from. This is the stable code branch.
* The `master` branch _should_ also be functional, but is where active development happens, so may be less stable. * The `master` branch _should_ also be functional, but is where active development happens, so may be less stable.
## Cross Compiling ## Cross Compiling
Cross compiling for things like `nodeup` are now done automatically via `make nodeup`. `make push-aws-run TARGET=admin@$TARGET` will automatically choose the linux amd64 build from your `.build` directory. Cross compiling for things like `nodeup` are now done automatically via `make nodeup`. `make push-aws-run TARGET=admin@$TARGET` will automatically choose the linux amd64 build from your `.build` directory.