Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 7ab35e2a2f Merge pull request #38397 from hoffin/master
Automatic merge from submit-queue

Correct docs

<!--  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**:
There was a change to the registry-proxy but the documentaiton wasn't completely updated to reflect change made.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
Linked to [contribute deis/registry-proxy as a replacement for kube-registry-proxy](https://github.com/kubernetes/kubernetes/pull/35797)

**Special notes for your reviewer**:
First time contributing.
**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
Updated the kube-registry-proxy readme example.
```
2016-12-08 22:49:20 -08:00
.github Fix PR template 2016-11-11 14:48:58 -08:00
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 #38397 from hoffin/master 2016-12-08 22:49:20 -08:00
cmd Merge pull request #38415 from liggitt/client-status 2016-12-08 20:37:58 -08:00
docs Update generated swagger/OpenAPI spec 2016-12-06 15:39:27 -08:00
examples Merge pull request #37145 from mstump/issue-34422-bump-cassandra-version 2016-12-08 04:39:22 -08:00
federation Update client status generator to not use json tags 2016-12-08 21:58:01 -05:00
Godeps Merge pull request #35116 from shashidharatd/fed-coredns-provider 2016-12-08 18:50:05 -08:00
hack Add --image-pull-progress-deadline option to kubelet 2016-12-09 09:28:57 +08:00
hooks Add pre-commit hooks for verifying pkg names 2016-11-30 15:23:36 +08:00
logo
pkg Merge pull request #38415 from liggitt/client-status 2016-12-08 20:37:58 -08:00
plugin Pass addressable values to DeepCopy 2016-12-08 14:16:01 -05:00
staging Merge pull request #37463 from tanshanshan/comment-modify 2016-12-08 00:23:13 -08:00
test Add --image-pull-progress-deadline option to kubelet 2016-12-09 09:28:57 +08:00
third_party
vendor Merge pull request #35116 from shashidharatd/fed-coredns-provider 2016-12-08 18:50:05 -08:00
.gazelcfg.json add a .gazelcfg 2016-11-28 16:48:11 -08:00
.generated_docs kubectl: generated changes for new pdb command 2016-12-02 18:42:25 +01:00
.generated_files List generated files for the github size munger 2016-11-15 15:47:22 -08:00
.gitattributes
.gitignore
BUILD
CHANGELOG.md Update CHANGELOG.md for v1.5.0-beta.3. 2016-12-08 14:59:45 -08:00
code-of-conduct.md
CONTRIBUTING.md updated munge-docs 2016-11-29 01:35:11 -08:00
labels.yaml
LICENSE LICENSE: revert modifications to Apache license 2016-11-22 11:44:46 -08:00
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 Additional cleanups and addressing review 2016-11-15 20:55:42 +01:00
Vagrantfile Customizable vagrant rsync args and excludes 2016-11-14 11:18:44 +01:00
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