github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/federation
History
Kubernetes Submit Queue 85e2e5dd9a Merge pull request #49642 from liggitt/rbac-v1 
Automatic merge from submit-queue (batch tested with PRs 49642, 50335, 50390, 49283, 46582)

Add rbac.authorization.k8s.io/v1

xref https://github.com/kubernetes/features/issues/2

Promotes the rbac.authorization.k8s.io/v1beta1 API to v1 with no changes

```release-note
The `rbac.authorization.k8s.io/v1beta1` API has been promoted to `rbac.authorization.k8s.io/v1` with no changes.
The `rbac.authorization.k8s.io/v1alpha1` version is deprecated and will be removed in a future release.
```
 		2017-08-10 00:53:17 -07:00
..
apis Merge pull request #49642 from liggitt/rbac-v1 2017-08-10 00:53:17 -07:00
client Update generated code 2017-08-06 15:32:28 +02:00
cluster [Federation] Update to enable all apis in e2e tests 2017-07-19 21:26:25 +05:30
cmd Merge pull request #49583 from irfanurrehman/fed-hpa-configTimeout 2017-08-09 14:14:27 -07:00
deploy
…
develop
…
docs/api-reference generated code 2017-08-09 15:19:47 -07:00
manifests
…
pkg Merge pull request #49642 from liggitt/rbac-v1 2017-08-10 00:53:17 -07:00
plugin/pkg/admission/schedulingpolicy [Federation]Fix forgeting to close file 2017-06-24 10:04:06 +08:00
registry/cluster Fix NotFound errors do not line up with API endpoint's group version 2017-08-07 16:30:40 +08:00
BUILD Auto generated files 2017-07-26 06:22:30 +05:30
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

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