768859404b
Automatic merge from submit-queue [Federation] Print out status updates while `kubefed init` is running This is not an ideal final state–it does not address the appearance of hanging during long-running commands, for example–but it provides some level of information when the operations are successful. See #41725. **Release note**: ```release-note Prints out status updates when running `kubefed init` ``` |
||
|---|---|---|
| .. | ||
| apis | ||
| client | ||
| cluster | ||
| cmd | ||
| deploy | ||
| develop | ||
| docs/api-reference | ||
| manifests | ||
| pkg | ||
| 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.