k3s/federation
Kubernetes Submit Queue 631612028a Merge pull request #37323 from nikhiljindal/firstClusterPR
Automatic merge from submit-queue

Fixing the logic to select first cluster in federated ingress controller

Ref https://github.com/kubernetes/kubernetes/issues/36074.

Before this change, ingress controller was using cluster with clusterIndex = 0 as the first cluster to create the ingress in.
But the ordering of clusters can change and hence ingress controller ended up creating the ingress in multiple clusters.
This PR fixes it by using an annotation on federated ingress. Controller now picks up a cluster randomly as the first cluster and creates ingress there. This clusters name is stored as an annotation on the federated ingress. Contoller does not create an ingress in any other cluster if this annotation is set on the federated ingress and IP has not been propagated. Once IP has been propagated, controller creates the ingress in all clusters.

cc @kubernetes/sig-cluster-federation @madhusudancs
2016-11-29 09:00:14 -08:00
..
apis Merge pull request #37091 from kargakis/doc-fix 2016-11-29 07:33:28 -08:00
client generated: refactor 2016-11-23 22:30:47 -06:00
cluster Fixing scripts to bring up federation control plane 2016-11-09 09:47:24 -08:00
cmd generated: refactor 2016-11-23 22:30:47 -06:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop rename build/ to build-tools/ 2016-10-24 14:41:56 -07:00
docs/api-reference generated: docs 2016-11-04 23:38:37 -04:00
manifests Fixing scripts to bring up federation control plane 2016-11-09 09:47:24 -08:00
pkg Merge pull request #37323 from nikhiljindal/firstClusterPR 2016-11-29 09:00:14 -08:00
registry/cluster autogenerated 2016-10-21 17:32:32 -07:00
Makefile Separate the build recipe in federation Makefile into separate phases. 2016-08-29 14:16:39 -07:00
OWNERS Add colhom to federation OWNERS 2016-06-27 13:16:43 -07: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