History

David Eads 0859798e8e update admission webhook to accept client config		2017-10-19 09:52:58 -04:00
..
apis	Update bazel	2017-10-18 17:24:04 +02:00
client	update BUILD files	2017-10-15 18:18:13 -07:00
cluster	Remove unnecessarily included scripts in federation deployment scripts	2017-09-26 10:41:18 +05:30
cmd	update admission webhook to accept client config	2017-10-19 09:52:58 -04:00
deploy	Update charts image version.	2016-10-12 00:15:01 -07:00
develop	Use buildozer to delete licenses() rules except under third_party/	2017-08-11 09:32:39 -07:00
docs/api-reference	Merge pull request #49205 from dixudx/fix_api_type_typos	2017-10-03 20:17:43 -07:00
pkg	Update bazel	2017-10-18 17:24:04 +02:00
plugin/pkg/admission/schedulingpolicy	Update bazel	2017-10-18 17:24:04 +02:00
registry/cluster	Update bazel	2017-10-18 17:24:04 +02:00
test	use multi-arch busybox for e2e	2017-10-19 10:36:31 +08:00
BUILD	Auto generated build files	2017-09-28 11:43:35 +05:30
Makefile	Separate the build recipe in federation Makefile into separate phases.	2016-08-29 14:16:39 -07:00
OWNERS	Add irfanurrehman as approver for federation.	2017-08-07 12:55:28 -07:00
README.md	fix bad url	2017-08-22 08:28:37 +08: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.