kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update the references to federation control plane images/binaries in the federation admin guide.

pull/945/head
Madhusudan.C.S 2016-08-01 11:32:15 -07:00
parent 9cb21fb737
commit 33b68cd102
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/admin/federation/index.md
View File

@ -17,8 +17,9 @@ This guide also assumes that we have the Kubernetes source code that can be
## Setting up a federation control plane ## Setting up a federation control plane
Setting up federation requires running the federation control plane which Setting up federation requires running the federation control plane which
consists of etcd, federation-apiserver and federation-controller-manager. consists of etcd, federation-apiserver (via hyperkube binary) and
We can run these binaries as pods on an existing Kubernetes cluster. federation-controller-manager (via hyperkube binary). We can run these
binaries as pods on an existing Kubernetes cluster.
### Getting images ### Getting images
@ -30,7 +31,9 @@ official release images or we can build from HEAD.
As part of every release, images are pushed to `gcr.io/google_containers`. To use As part of every release, images are pushed to `gcr.io/google_containers`. To use
these images, we set env var `FEDERATION_PUSH_REPO_BASE=gcr.io/google_containers` these images, we set env var `FEDERATION_PUSH_REPO_BASE=gcr.io/google_containers`
This will always use the latest image. This will always use the latest image.
To use federation-apiserver and federation-controller-manager images from a specific release, we can set `FEDERATION_IMAGE_TAG`. To use the hyperkube image which includes federation-apiserver and
federation-controller-manager from a specific release, we can set
`FEDERATION_IMAGE_TAG`.
#### Building and pushing images from HEAD #### Building and pushing images from HEAD