k3s/federation
Kubernetes Submit Queue c523476d6f Merge pull request #40124 from mbohlool/separation
Automatic merge from submit-queue

Use full package path for definition name in OpenAPI spec

We were using short package name (last part of package name) plus type name for OpenAPI spec definition name. That can result in duplicate names and make the spec invalid. To be sure we will always have unique names, we are going to use full package name as definition name. Also "x-kubernetes-tag" custom field is added to definitions to list Group/Version/Kind for the definitions that has it. This will help clients to discover definitions easier.
Lastly, we've added a reference from old definition names to the new ones to keep backward compatibilities. The list of old definitions will not be updated.

**Release note**:
- Rename OpenAPI definition names to type's full package names to prevent duplicates
- Create OpenAPI extension "x-kubernetes-group-version-kind" for definitions to store Group/Version/Kind
- Deprecate old definition names and create a reference to the new definitions. Old definitions will be removed in the next release.
2017-02-01 12:06:39 -08:00
..
apis Update generated OpenAPI specs 2017-01-30 20:05:20 -08:00
client Regenerate clients 2017-01-31 11:16:27 -05:00
cluster Replace + with _ in the image tag version since + is not a valid image tag character. 2017-01-30 12:44:57 -08:00
cmd Merge pull request #40124 from mbohlool/separation 2017-02-01 12:06:39 -08:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop Add a wrapper script to locate the kubefed binary in a CI environment. 2017-01-27 13:52:22 -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 #36734 from YuPengZTE/devPunctuation 2017-02-01 02:55:48 -08:00
registry/cluster move pkg/storage to apiserver 2017-01-31 19:07:33 -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 Propose adding quinton-hoole to federation/OWNERS 2017-01-24 17:13:16 -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