8d6bbaa85f
Automatic merge from submit-queue Timeout and Max-in-flight don't report non-resource URLs correctly. Unify error reporting for 429 and 504 to be correct for timeout and max in flight and eviction. Add better messages to eviction (removing a todo). Return the correct body content for timeouts (reason and code should be correct). This potentially increases cardinality of 429, but because non-api urls may be under the max-inflight budget we need to report them somewhere (if something breaks and starts fetching API versions endlessly). ```release-note The 504 timeout error was returning a JSON error body that indicated it was a 500. The body contents now correctly report a 500 error. ``` |
||
|---|---|---|
| .. | ||
| 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.