github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
f9777522433b10b286605eca1371062df943f335
kubernetes/federation
History
Kubernetes Submit Queue 13305ef0ff Merge pull request #31139 from nikhiljindal/namespaceAdmissionControl 
Automatic merge from submit-queue

federation: Adding support for namespace admission controls in federation-apiserver

Now that we have namespaces in federation apiserver, we can support namespace admission controls.

There are 3 of these:
namespace/autoprovision, namespace/exists and namespace/lifecycle.
namespace/autoprovision, namespace/exists should be deprecated in kubernetes(https://github.com/kubernetes/kubernetes/issues/31195). Adding support for namespace/lifecycle to federation-apiserver.
As in kube-apiserver, enabling namespace/lifecycle by default.


```release-note
Action required: If you have a running federation control plane, you will have to ensure that for all federation resources, the corresponding namespace exists in federation control plane.

federation-apiserver now supports NamespaceLifecycle admission control, which is enabled by default. Set the --admission-control flag on the server to change that.
```

cc @kubernetes/sig-cluster-federation @quinton-hoole
2016-08-23 00:19:08 -07:00
..
apis
Merge pull request #30823 from nikhiljindal/swaggerDocs
2016-08-20 18:09:58 -07:00
client
Adding events to federation clientset and adding an e2e
2016-08-12 17:47:49 -07:00
cluster
Fixing/updating e2e tests
2016-08-22 21:49:34 -07:00
cmd
Merge pull request #31139 from nikhiljindal/namespaceAdmissionControl
2016-08-23 00:19:08 -07:00
manifests
Enabling namespace admission controls
2016-08-22 17:28:03 -07:00
pkg
Add Federated Ingress Controller.
2016-08-22 12:59:54 -07:00
registry/cluster
generic.Matcher -> *generic.SelectionPredicate
2016-08-13 21:52:11 -07:00
build.sh
Switch tab indentation to two spaces.
2016-08-10 23:52:42 -07:00
config.default.json
Implement a build and deploy script to turn up/down federation.
2016-08-10 23:24:38 -07:00
Makefile
Implement a build and deploy script to turn up/down federation.
2016-08-10 23:24:38 -07:00
OWNERS
Add colhom to federation OWNERS
2016-06-27 13:16:43 -07:00
README.md
Add a TODO to re-evaluate jq dependency.
2016-08-10 23:47:29 -07:00

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

  1. Split the build phase (make recipe) into multiple phases:

    1. init: pull installer images
    2. build-binaries
    3. build-docker
    4. build: build-binary + build-docker
    5. push: to push the built images
    6. genconfig
    7. deploy-clusters
    8. deploy-federation
    9. deploy: deploy-clusters + deploy-federation
    10. destroy-federation
    11. destroy-clusters
    12. destroy: destroy-federation + destroy-clusters
    13. redeploy-federation: just redeploys the federation components.

  2. Add a release phase to run as part of Kubernetes release process that copies only a part of the build.sh script that's relevant to the users into the release.

  3. 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.

Analytics