kubernetes/federation
2017-01-22 12:40:45 +05:30
..
apis [Federation] Expose autoscaling apis through federation api server 2017-01-22 12:40:45 +05:30
client [Federation] Expose autoscaling apis through federation api server 2017-01-22 12:40:45 +05:30
cluster Read the VERSIONS file for the FEDERATION_IMAGE_TAG value. 2017-01-19 15:44:35 -08:00
cmd [Federation] Register autoscaling apis to federation api server 2017-01-22 12:27:56 +05:30
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop Build release tarballs in bazel and add make bazel-release rule 2017-01-13 16:17:44 -08:00
docs/api-reference generated: change to WatchEvent from Event 2017-01-06 23:45:05 -05:00
manifests use etcd2 as storage-backend for federation until it is completely tested with etcd3 2017-01-10 15:14:40 +05:30
pkg Merge pull request #40235 from deads2k/generic-26-listers 2017-01-20 14:22:51 -08:00
registry/cluster move pkg/fields to apimachinery 2017-01-19 09:50:16 -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 Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
README.md Fix doc links in Federation readme 2016-11-07 11:31:08 +00:00

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

  1. 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.

Analytics