Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue aa8a03ef07 Merge pull request #35797 from bacongobbler/registry-proxy
Automatic merge from submit-queue (batch tested with PRs 32663, 35797)

contribute deis/registry-proxy as a replacement for kube-registry-proxy

This PR is a proposal to replace the `kube-registry-proxy` addon code with [deis/registry-proxy](https://github.com/deis/registry-proxy). We have been running this component in production for several months ([since Workflow v2.3.0](15d4c1c298/workflow-v2.3.0/tpl/deis-registry-proxy-daemon.yaml)) without any issues.

There are several benefits that this proxy provides over the current implementation:
- it's the same code that is provided in [docker/distribution's contrib dir](https://github.com/docker/distribution/tree/master/contrib/compose) which I have personally used for both Docker v1 and v2 engine deployments without any issues
- the ability to [disable old Docker clients](https://github.com/deis/registry-proxy/blob/master/rootfs/etc/nginx/conf.d/default.conf.in#L19-L23) that are incompatible with the v2 registry
- better default connection timeouts, using best practices from the Docker community as a whole
- workarounds for bugs like https://github.com/docker/docker/issues/1486 (see https://github.com/deis/registry-proxy/blob/master/rootfs/etc/nginx/conf.d/default.conf.in#L15-L16)

Things that this PR differs from the current implementation:
- it's not HAProxy.

I'm not sure how the release process goes for this component, but I bumped the version to v0.4 and changed the maintainer to myself considering this is a massive overhaul. Please let me know if this is acceptable as a replacement or if we should perhaps consider this as an alternative implementation.

Happy Friday!
2016-12-07 21:59:11 -08:00
.github
api Update generated swagger/OpenAPI spec 2016-12-06 15:39:27 -08:00
build-tools Add support for cross-compiling s390x binaries 2016-12-07 14:51:08 +05:30
cluster Merge pull request #35797 from bacongobbler/registry-proxy 2016-12-07 21:59:11 -08:00
cmd Merge pull request #36735 from YuPengZTE/devHTTP 2016-12-07 16:21:21 -08:00
docs Update generated swagger/OpenAPI spec 2016-12-06 15:39:27 -08:00
examples Merge pull request #38128 from elsonrodriguez/rbd-docs-secret-fix 2016-12-07 03:09:32 -08:00
federation Merge pull request #37693 from wojtek-t/pipe_get_options_to_storage 2016-12-07 00:52:26 -08:00
Godeps Merge pull request #32663 from anguslees/extraroutes 2016-12-07 21:36:13 -08:00
hack Merge pull request #38258 from derekwaynecarr/kernel-memcg-flag 2016-12-07 15:00:10 -08:00
hooks
logo
pkg Merge pull request #32663 from anguslees/extraroutes 2016-12-07 21:36:13 -08:00
plugin Merge pull request #35101 from xilabao/auth-duplicate-detect 2016-12-07 07:27:13 -08:00
staging generated: staging update 2016-12-03 19:10:55 -05:00
test Merge pull request #37850 from MrHohn/gke-dns-autoscale 2016-12-07 18:13:11 -08:00
third_party
vendor Merge pull request #32663 from anguslees/extraroutes 2016-12-07 21:36:13 -08:00
.gazelcfg.json
.generated_docs kubectl: generated changes for new pdb command 2016-12-02 18:42:25 +01:00
.generated_files
.gitattributes
.gitignore
BUILD
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
labels.yaml
LICENSE
Makefile Add "make help" to list all make targets and help info 2016-12-05 02:00:46 -05:00
Makefile.generated_files
OWNERS
OWNERS_ALIASES
README.md
Vagrantfile
WORKSPACE

Kubernetes

Submit Queue Widget GoDoc Widget Coverage Status Widget

Introduction

Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications. Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF)

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.


Are you ...

Code of Conduct

The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Community

Do you want to help "shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented? ". If you are a company, you should consider joining the CNCF. For details about who's involved in CNCF and how Kubernetes plays a role, read the announcement. For general information about our community see the website community page.

Join us on social media (Twitter, Google+) and read our blog

Ask questions and help answer them on Slack or Stack Overflow

Attend our key events (kubecon, cloudnativecon, weekly community meeting)

Join a Special Interest Group (SIG)

Contribute

If you're interested in being a contributor and want to get involved in developing Kubernetes, get started with with this reading:

You will then most certainly gain a lot from joining a SIG, attending the regular hangouts as well as the community meeting.

If you have an idea for a new feature, see the Kubernetes Features repository for a list of features that are coming in new releases as well as details on how to propose one.

Support

While there are many different channels that you can use to get hold of us (Slack, Stack Overflow, Issues, Forums/Mailing lists), you can help make sure that we are efficient in getting you the help that you need.

If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another. We don't bite!

Analytics