2c2c92659a
Automatic merge from submit-queue (batch tested with PRs 45374, 44537, 45739, 44474, 45888) Update 'More info' links on API types and fields > **Please just review the first commit, the rest is generated files.** Recent docs website shuffling during 1.6 caused majority of links in the API types and fields to break. Since we do not have server-side 301 redirects, user has to click an extra link, and the #target fragment in the URL will be lost. (This is because GitHub’s redirect_from feature is not ideal.) For the time being, I have manually gone through all of them to bring them up to date and add HTTPS to those missing it. This is a docs-only change and impacts generated code, generated swaggers, API reference docs etc. cc: @steveperry-53 @devin-donnelly @chenopis fyi, docs links changes (even small title changes) easily breaks links in API reference, Swagger, kubectl explain, and many other places. Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
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.