k3s/federation
Clayton Coleman 35a6bfbcee
generated: refactor
2016-11-23 22:30:47 -06:00
..
apis generated: refactor 2016-11-23 22:30:47 -06:00
client generated: refactor 2016-11-23 22:30:47 -06:00
cluster Fixing scripts to bring up federation control plane 2016-11-09 09:47:24 -08:00
cmd generated: refactor 2016-11-23 22:30:47 -06:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop rename build/ to build-tools/ 2016-10-24 14:41:56 -07:00
docs/api-reference generated: docs 2016-11-04 23:38:37 -04:00
manifests Fixing scripts to bring up federation control plane 2016-11-09 09:47:24 -08:00
pkg generated: refactor 2016-11-23 22:30:47 -06:00
registry/cluster autogenerated 2016-10-21 17:32:32 -07:00
Makefile Separate the build recipe in federation Makefile into separate phases. 2016-08-29 14:16:39 -07:00
OWNERS Add colhom to federation OWNERS 2016-06-27 13:16:43 -07:00
README.md Federation README typo fix. 2016-08-29 14:17:42 -07: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

  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