82b3a80ad1
Automatic merge from submit-queue (batch tested with PRs 50016, 49583, 49930, 46254, 50337) [Federation] Make the hpa scale time window configurable This PR is on top of open pr https://github.com/kubernetes/kubernetes/pull/45993. Please review only the last commit in this PR. This adds a config param to controller manager, the value of which gets passed to hpa adapter via sync controller. This is needed to reduce the overall time limit of the hpa scaling window to much lesser (then the default 2 mins) to get e2e tests run faster. Please see the comment on the newly added parameter. **Special notes for your reviewer**: @kubernetes/sig-federation-pr-reviews @quinton-hoole @marun to please validate the mechanism used to pass a parameter from cmd line to adapter. **Release note**: ``` federation-controller-manager gets a new flag --hpa-scale-forbidden-window. This flag is used to configure the duration used by federation hpa controller to determine if it can move max and/or min replicas around (or not), of a cluster local hpa object, by comparing current time with the last scaled time of that cluster local hpa. Lower value will result in faster response to scalibility conditions achieved by cluster local hpas on local replicas, but too low a value can result in thrashing. Higher values will result in slower response to scalibility conditions on local replicas. ``` |
||
|---|---|---|
| .. | ||
| 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.