![]() Automatic merge from submit-queue Support for preexisting replicas and estimated capacity in federated replicaset controller With this PR the planer will be able to: * Keep already existing replicas in their current clusters if rebalance = false and min/max boundaries are met. * Limit the number of replicas in a cluster to the level that was measured by the count of running and unschedulable pods. And provide an estimate how much more pods would be nice to put in a cluster so that if they are scheduled we will be closer to the desired layout or to schedule the desired number of replicas at all. cc: @quinton-hoole @jianhuiz @wojtek-t @kubernetes/sig-cluster-federation |
||
---|---|---|
.. | ||
apis | ||
client | ||
cluster | ||
cmd | ||
manifests | ||
pkg | ||
registry/cluster | ||
Makefile | ||
OWNERS | ||
README.md | ||
build.sh | ||
config.default.json |
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 should be as simple as running:
make build do=gen
To deploy clusters and install federation components, edit the
config.default.json
file to describe your clusters and run
make build do=deploy
To turn down the federation components and tear down the clusters run:
make build do=destroy
Ideas for improvement
-
Split the
build
phase (make recipe) into multiple phases:init
: pull installer imagesbuild-binaries
build-docker
build
: build-binary + build-dockerpush
: to push the built imagesgenconfig
deploy-clusters
deploy-federation
deploy
: deploy-clusters + deploy-federationdestroy-federation
destroy-clusters
destroy
: destroy-federation + destroy-clustersredeploy-federation
: just redeploys the federation components.
-
Add a
release
phase to run as part of Kubernetes release process that copies only a part of thebuild.sh
script that's relevant to the users into the release. -
Continue with
destroy
phase even in the face of errors.The bash script sets
set -e errexit
which causes the script to exit at the very first error. This should be the default mode for deploying components but not for destroying/cleanup.