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 419d38a965 Merge pull request #40516 from shashidharatd/kubefed-1 
Automatic merge from submit-queue

[Federation][kubefed] Add option to expose federation apiserver on nodeport service

**What this PR does / why we need it**:
This PR adds an option to kubefed to expose federation api server over nodeport. This can be useful to deploy federation in non-cloud environments. This PR is target to address #39271

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```
[Federation] kubefed init learned a new flag, `--api-server-service-type`, that allows service type to be specified for the federation API server.
[Federation] kubefed init also learned a new flag, `--api-server-advertise-address`, that allows specifying advertise address for federation API server in case the service type is NodePort.
```

@kubernetes/sig-federation-misc @madhusudancs
 		2017-02-05 12:48:33 -08:00
..
apis Init containers in GA - generated code 2017-02-03 01:08:25 +01:00
client Regenerate clients 2017-01-31 11:16:27 -05:00
cluster Replace + with _ in the image tag version since + is not a valid image tag character. 2017-01-30 12:44:57 -08:00
cmd Update generated files 2017-02-03 08:15:46 +01:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop Merge pull request #40809 from rrati/federation-build-local 2017-02-02 18:53:48 -08:00
docs/api-reference Init containers in GA - generated code 2017-02-03 01:08:25 +01:00
manifests Remove federated-image.tag from the .gitignore file. 2017-01-20 00:58:42 -08:00
pkg Merge pull request #40516 from shashidharatd/kubefed-1 2017-02-05 12:48:33 -08:00
registry/cluster Update generated files 2017-02-03 08:15:46 +01:00
BUILD Build release tarballs in bazel and add `make bazel-release` rule 2017-01-13 16:17:44 -08:00
Makefile Separate the build recipe in federation Makefile into separate phases. 2016-08-29 14:16:39 -07:00
OWNERS Propose adding quinton-hoole to federation/OWNERS 2017-01-24 17:13:16 -08:00
README.md Fix doc links in Federation readme 2016-11-07 11:31:08 +00: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 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