k3s/federation
Kubernetes Submit Queue b59ad9cbff Merge pull request #50146 from gmarek/deepcopyinto
Automatic merge from submit-queue (batch tested with PRs 46512, 50146)

Make metav1.(Micro)?Time functions take pointers

Is there any reason for those functions not to be on pointers?
2017-08-19 11:28:15 -07:00
..
apis auto-gen 2017-08-18 11:07:35 +08:00
client Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07:00
cluster Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07:00
cmd add validation for fed-apiserver 2017-08-12 20:04:14 +08: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 auto-gen 2017-08-18 11:07:35 +08:00
manifests Release 3.0.17 etcd image 2017-02-27 16:23:44 +01:00
pkg Make metav1.(Micro)?Time functions take pointers 2017-08-17 11:24:28 +02:00
plugin/pkg/admission/schedulingpolicy Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07:00
registry/cluster Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07:00
BUILD Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07: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 federation:update outdated link 2017-05-08 09:07:40 +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

  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