github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
a79f714b1e00f8fb7911f5eb6e131eb863fd1f95
kubernetes/federation
History
Kubernetes Submit Queue 961ef2b51d Merge pull request #31470 from caesarxuchao/regenerate-release-1-4 
Automatic merge from submit-queue

Fix missing expansion files in clientset release 1.4

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md
2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md
3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes
-->

**What this PR does / why we need it**:
Fix missing expansion files in clientset release 1.4;
Update the client-gen tool to automatically update generated_expansion.go;
Update the readme to document the best practice of using client-gen.

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

https://github.com/kubernetes/kubernetes/issues/29698#issuecomment-241315798


**Special notes for your reviewer**:

**Release note**:
<!--  Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access) 
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. 
-->
```release-note
```

cc @lavalamp @krousey @mbohlool
2016-08-27 00:45:52 -07:00
..
apis
add generated files
2016-08-22 23:00:23 -07:00
client
run client-gen
2016-08-26 10:55:22 -07:00
cluster
Limit sourcing the build scripts only for build/push phase of federation control plane components.
2016-08-25 14:29:55 -07:00
cmd
Merge pull request #31139 from nikhiljindal/namespaceAdmissionControl
2016-08-23 00:19:08 -07:00
manifests
[Federation] Do not build separate binaries for federation control plane components, hyperkube should be sufficient.
2016-08-25 14:29:32 -07:00
pkg
Increase log level for debug infos in Federated ReplicaSet controller
2016-08-26 17:39:06 +02:00
registry/cluster
Merge pull request #31390 from hongchaodeng/fix
2016-08-25 16:44:10 -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