federation

by kubernetes-retired

kubernetes-retired / federation

[EOL] Cluster Federation

204 Stars 81 Forks Last release: Not found Apache License 2.0 15.0K Commits 5 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Cluster Federation

Kubernetes Cluster Federation enables users to federate multiple Kubernetes clusters. To know more details about the same please see the user guide.

Deploying Kubernetes Cluster Federation

The prescribed mechanism to deploy Kubernetes Cluster Federation is using kubefed. A complete guide for the same is available at setup cluster federation using kubefed.

Building Kubernetes Cluster Federation

Building cluster federation binaries, which include fcp (short for federation control plane) and kubefed should be as simple as running:

shell
make

A kubernetes like release packages can also be built using:

shell
make quick-release

The '

kubefed
binary can be found in
federation-client-*.tar.gz
. The
fcp
binary, which self contains
federation-apiserver
and
federation-controller-manager
can be found in
federation-server-*.tar.gz
.
federation-server-*.tar.gz
includes
fcp-*.tar
, which is the fcp docker image in the tar format and can be consumed by the
kubefed
tool.

To run the docker image load the container on your build machine and push to your repository: ```shell

Run from $GOPATH/src/k8s.io/kubernetes/federation

docker load -i _output/release-images/amd64/fcp-amd64.tar

Tag to your REGISTRY/REPO/IMAGENAME[:TAG]

docker docker tag gcr.io/googlecontainers/fcp-amd64:v1.9.0-alpha.2.60430416309f9e58-dirty REGISTRY/REPO/IMAGENAME[:TAG]

push to your registry

docker push REGISTRY/REPO/IMAGENAME[:TAG] ```

then bring up the new control plane:

shell
_output/dockerized/bin/linux/amd64/kubefed init myfed --host-cluster-context=HOST_CLUSTER_CONTEXT --image=REGISTRY/REPO/IMAGENAME[:TAG] --dns-provider="PROVIDER" --dns-zone-name="YOUR_ZONE" --dns-provider-config=/path/to/provider.conf

A note to the reader

Kubernetes federation code is in a state of flux. Since its incubation, it lived in core kubernetes repo. The same now is maturing into its own placeholder. The process of this movement is not yet complete. It already borrows a lot of code from its earlier parent, especially build infrastructure and utility scripts. This will be cleaned up and simplified. Subsequently we will also concentrate our efforts into cleaning issues and problems reported on existing features, with a focus of moving atleast a subset of all federation features towards GA. Please raise an issue, in case you find problems and we welcome developers to participate in this effort.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.