k3s/federation
Kubernetes Submit Queue d6fb8b06dd Merge pull request #31231 from mwielgus/rs-fix3
Automatic merge from submit-queue

Test if 2 federated informers in rs controller are in sync

cc: @quinton-hoole @kubernetes/sig-cluster-federation
2016-08-23 08:04:11 -07:00
..
apis add generated files 2016-08-22 23:00:23 -07:00
client Adding events to federation clientset and adding an e2e 2016-08-12 17:47:49 -07:00
cluster Fixing/updating e2e tests 2016-08-22 21:49:34 -07:00
cmd Merge pull request #31139 from nikhiljindal/namespaceAdmissionControl 2016-08-23 00:19:08 -07:00
manifests Enabling namespace admission controls 2016-08-22 17:28:03 -07:00
pkg Merge pull request #31231 from mwielgus/rs-fix3 2016-08-23 08:04:11 -07:00
registry/cluster generic.Matcher -> *generic.SelectionPredicate 2016-08-13 21:52:11 -07:00
Makefile Implement a build and deploy script to turn up/down federation. 2016-08-10 23:24:38 -07:00
OWNERS Add colhom to federation OWNERS 2016-06-27 13:16:43 -07:00
README.md Add a TODO to re-evaluate jq dependency. 2016-08-10 23:47:29 -07:00
build.sh Switch tab indentation to two spaces. 2016-08-10 23:52:42 -07:00
config.default.json Implement a build and deploy script to turn up/down federation. 2016-08-10 23:24:38 -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 should be as simple as running:

make build do=gen

To deploy clusters and install federation components, edit the config.default.json file to describe your clusters and run

make build do=deploy

To turn down the federation components and tear down the clusters run:

make build do=destroy

Ideas for improvement

  1. Split the build phase (make recipe) into multiple phases:

    1. init: pull installer images
    2. build-binaries
    3. build-docker
    4. build: build-binary + build-docker
    5. push: to push the built images
    6. genconfig
    7. deploy-clusters
    8. deploy-federation
    9. deploy: deploy-clusters + deploy-federation
    10. destroy-federation
    11. destroy-clusters
    12. destroy: destroy-federation + destroy-clusters
    13. redeploy-federation: just redeploys the federation components.
  2. Add a release phase to run as part of Kubernetes release process that copies only a part of the build.sh script that's relevant to the users into the release.

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