github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/federation
History
Kubernetes Submit Queue dd4de1e7d4 Merge pull request #39956 from justinsb/dnsprovider_isempty 
Automatic merge from submit-queue

dnsprovider: Add IsEmpty method

When batching changes, it is often handy to know whether a changeset
IsEmpty, and thus does not need to be Apply-ed.

```release-note
NONE
```
 		2017-01-25 15:07:32 -08:00
..
apis Merge pull request #37055 from mbohlool/dev 2017-01-25 00:07:40 -08:00
client make tools/cache authoritative 2017-01-25 08:29:45 -05:00
cluster Read the VERSIONS file for the FEDERATION_IMAGE_TAG value. 2017-01-19 15:44:35 -08:00
cmd Update generated files 2017-01-24 20:56:03 +01:00
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: api 2017-01-23 12:26:35 -05:00
manifests Remove federated-image.tag from the .gitignore file. 2017-01-20 00:58:42 -08:00
pkg Merge pull request #39956 from justinsb/dnsprovider_isempty 2017-01-25 15:07:32 -08:00
registry/cluster refactor: move ListOptions references to metav1 2017-01-23 17:52:46 -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 New Federation team. 2017-01-23 15:11: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