github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d8205661b7
kubernetes/federation
History
Kubernetes Submit Queue eae2917402 Merge pull request #46283 from ktsakalozos/feature/nodeport-port 
Automatic merge from submit-queue

Adding option to set the federation api server port if nodeport is set

**What this PR does / why we need it**: Kubefed will deploy the respected services and then it will do a health check. Prior to this patch if the user selects the nodeport a random port is opened. In environments where firewalls are in place this random port selection will cause the health check to fail. With this patch we enable users to designate a specific port, after for example opening it on their firewall.    

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

**Special notes for your reviewer**:

**Release note**: 

```
Kubefed init allows for setting port in Nodeport configuration
```
2017-07-30 04:01:36 -07:00
..
apis Merge pull request #49192 from mfojtik/unify-clientgen-tags 2017-07-25 02:43:13 -07:00
client Remove federation internal clienset 2017-07-26 06:22:30 +05:30
cluster [Federation] Update to enable all apis in e2e tests 2017-07-19 21:26:25 +05:30
cmd Merge pull request #43443 from irfanurrehman/kubefed-doc-1 2017-07-25 21:52:45 -07:00
deploy Update charts image version. 2016-10-12 00:15:01 -07:00
develop Revert "[Federation] Build a simple hyperkube image on-the-fly only containing the hyperkube binary for development and testing purposes." 2017-04-24 22:26:20 -07:00
docs/api-reference Update swagger and OpenAPI spec 2017-07-24 17:28:29 -07:00
manifests Release 3.0.17 etcd image 2017-02-27 16:23:44 +01:00
pkg Merge pull request #46283 from ktsakalozos/feature/nodeport-port 2017-07-30 04:01:36 -07:00
plugin/pkg/admission/schedulingpolicy [Federation]Fix forgeting to close file 2017-06-24 10:04:06 +08:00
registry/cluster Grow signature for predicate attributes to include init status 2017-06-02 22:09:04 -04:00
BUILD Auto generated files 2017-07-26 06:22:30 +05:30
Makefile Separate the build recipe in federation Makefile into separate phases. 2016-08-29 14:16:39 -07:00
OWNERS fed: Add marun as reviewer 2017-02-09 09:50:57 -08:00
README.md federation:update outdated link 2017-05-08 09:07:40 +08: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