b8b5c68c19
Automatic merge from submit-queue (batch tested with PRs 43005, 46660, 46385, 46991, 47103) Ignore `daemonset-controller-hash` label key in federation before comparing the federated object with its cluster equivalent. Kubernetes daemonset controller writes a daemonset's hash to the object label as an optimization to avoid recomputing it every time. Adding a new label to the object that the federation is unaware of causes problems because federated controllers compare the objects in federation and their equivalents in clusters and try to reconcile them. This leads to a constant fight between the federated daemonset controller and the cluster controllers, and they never reach a stable state. Ideally, cluster components should not update an object's spec or metadata in a way federation cannot replicate. They can update an object's status though. Therefore, this daemonset hash should be a field in daemonset's status, not a label in object meta. @janetkuo says that this label is only a short term solution. In the near future, they are going to replace it with revision numbers in daemonset status. We can then rip this bandaid out. Fixes #46925 **Release note**: ```release-note NONE ``` /assign @csbell /cc @shashidharatd @marun @nikhiljindal @perotinus /sig federation |
||
|---|---|---|
| .. | ||
| apis | ||
| client | ||
| cluster | ||
| cmd | ||
| deploy | ||
| develop | ||
| docs/api-reference | ||
| manifests | ||
| pkg | ||
| plugin/pkg/admission/schedulingpolicy | ||
| registry/cluster | ||
| BUILD | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
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
-
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.