k3s/federation
Maru Newby 02a294533b fed: Fix flakey ingress unit test
The unit test for the ingress controller was previously adding
a cluster twice, which resulted in a cluster being deleted and added
back.  The deletion was racing the controller shutdown to close
informer channels.  This change ensures that the informer clears its
map of informers when Stop() is called to prevent a double close, and
that the test no longer adds the cluster twice.
2017-03-13 13:18:06 -07:00
..
apis Update docs and client 2017-03-09 07:34:56 +00:00
client Update client 2017-02-28 15:34:34 +01:00
cluster Merge pull request #42851 from madhusudancs/fed-down-improvements 2017-03-12 16:29:37 -07:00
cmd fed: Create integration test fixture for api 2017-03-08 06:58:58 -08:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop Move push-federation-images.sh to federation and implement similar functionality in jenkins build directory for presubmits. 2017-02-27 17:54:37 -08:00
docs/api-reference generated codes. 2017-03-02 11:15:17 +08:00
manifests Release 3.0.17 etcd image 2017-02-27 16:23:44 +01:00
pkg fed: Fix flakey ingress unit test 2017-03-13 13:18:06 -07:00
registry/cluster Updating the registry to return whether the resource was immediately deleted 2017-02-21 11:00:35 -08: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 fed: Add marun as reviewer 2017-02-09 09:50:57 -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

  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