70a268528e
Automatic merge from submit-queue (batch tested with PRs 42058, 41160, 42065, 42076, 39338) [Federation] Create configmap for the cluster kube-dns when cluster joins and remove when it unjoins This PR implements the functionality as needed in https://github.com/kubernetes/kubernetes/issues/38400 cc @kubernetes/sig-cluster-federation @nikhiljindal @madhusudancs **Release note**: ``` kubefed join can now automatically create a configmap or add information to already existing one, storing this federation name vs zone name information in the joining cluster. Further kubefed unjoin can remove this configmap or only this information from the configmap, if the unjoin cluster is registered with multiple federations. The name of the configmap is kube-dns and the information in it is consumed by the in-cluster dns server. ```
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
-
Continue with
destroyphase even in the face of errors.The bash script sets
set -e errexitwhich causes the script to exit at the very first error. This should be the default mode for deploying components but not for destroying/cleanup.