History

deads2k c9a008dff3 move util/intstr to apimachinery		2017-01-30 12:46:59 -05:00
..
apis	move util/intstr to apimachinery	2017-01-30 12:46:59 -05:00
client	move testing/core to client-go	2017-01-26 13:54:40 -05:00
cluster	Use a wrapper script to locate kubefed and kubectl binaries instead of directly constructing their paths.	2017-01-27 13:52:22 -08:00
cmd	move genericapiserver/server/filters to apiserver	2017-01-27 08:49:30 -05:00
deploy	Update charts image version.	2016-10-12 00:15:01 -07:00
develop	Add a wrapper script to locate the kubefed binary in a CI environment.	2017-01-27 13:52:22 -08:00
docs/api-reference	generated: api	2017-01-23 12:26:35 -05:00
manifests	Remove federated-image.tag from the .gitignore file.	2017-01-20 00:58:42 -08:00
pkg	move util/intstr to apimachinery	2017-01-30 12:46:59 -05:00
registry/cluster	remove storage dependency on api	2017-01-27 14:02:28 -05:00
BUILD	Build release tarballs in bazel and add `make bazel-release` rule	2017-01-13 16:17:44 -08:00
Makefile	Separate the build recipe in federation Makefile into separate phases.	2016-08-29 14:16:39 -07:00
OWNERS	Propose adding quinton-hoole to federation/OWNERS	2017-01-24 17:13:16 -08:00
README.md	Fix doc links in Federation readme	2016-11-07 11:31:08 +00:00

README.md

Cluster Federation

Kubernetes Cluster Federation enables users to federate multiple Kubernetes clusters. Please see the user guide and the admin guide for more details about setting up and using the Cluster Federation.

Building Kubernetes Cluster Federation

Please see the Kubernetes Development Guide for initial setup. Once you have the development environment setup as explained in that guide, you also need to install jq

Building cluster federation artifacts should be as simple as running:

make build

You can specify the docker registry to tag the image using the KUBE_REGISTRY environment variable. Please make sure that you use the same value in all the subsequent commands.

To push the built docker images to the registry, run:

make push

To initialize the deployment run:

(This pulls the installer images)

make init

To deploy the clusters and install the federation components, edit the ${KUBE_ROOT}/_output/federation/config.json file to describe your clusters and run:

make deploy

To turn down the federation components and tear down the clusters run:

make destroy

Ideas for improvement

Continue with destroy phase even in the face of errors.

The bash script sets set -e errexit which causes the script to exit at the very first error. This should be the default mode for deploying components but not for destroying/cleanup.