Go to file
Jared 9d6890889f
Update volume.yaml
2017-12-05 14:41:38 -06:00
.github PR template note for 1.9 (#5943) 2017-10-19 09:44:15 -07:00
_data Update volume.yaml 2017-12-05 14:41:38 -06:00
_includes update Kublr blurb 2017-12-04 21:22:13 -05:00
_layouts Remove 'Create an Issue' button on docs/setup page (#6214) 2017-11-07 16:56:56 -08:00
_plugins Fix/re-introduce custom Jekyll tags for better glossary integration (#6163) 2017-11-06 15:36:24 -06:00
_sass Resolves responsive styling issues with button, in the video section (#6280) 2017-11-13 16:29:29 -08:00
case-studies Rename Google Container Engine to Google Kubernetes Engine 2017-11-13 13:43:14 -08:00
cn Merge pull request #6549 from potterhe/potterhe/cn_corrigendum 2017-12-05 09:40:21 +08:00
community Updates to Partner Page and Kubecon Banners 2017-11-24 11:35:15 +11:00
css Fix/re-introduce custom Jekyll tags for better glossary integration (#6163) 2017-11-06 15:36:24 -06:00
docs Merge pull request #6545 from surajssd/fix-hpa-declarative-instructions 2017-12-05 16:51:04 +08:00
images Updates to KCSP and Conformance Partners (#6551) 2017-12-04 13:41:03 -06:00
js Fix/re-introduce custom Jekyll tags for better glossary integration (#6163) 2017-11-06 15:36:24 -06:00
partners Updates to Partner Page and Kubecon Banners 2017-11-24 11:35:15 +11:00
staging-container
test Rewrite PodSecurityPolicy guide 2017-12-01 15:44:23 -08:00
.gitignore
.travis.yml Change repo name to website. (#6076) 2017-10-27 10:47:03 -07:00
404.md
CONTRIBUTING.md delete redundant space 2017-10-19 17:06:33 +08:00
Gemfile Fix/re-introduce custom Jekyll tags for better glossary integration (#6163) 2017-11-06 15:36:24 -06:00
Gemfile.lock Fix/re-introduce custom Jekyll tags for better glossary integration (#6163) 2017-11-06 15:36:24 -06:00
LICENSE
Makefile
OWNERS Remove chenopis from OWNERS file 2017-11-01 11:54:15 -07:00
README.md Fixes issue #5620 (#5869) 2017-10-23 15:08:47 -07:00
_config.yml Rename `gems` to `plugins` in `/_config.yml` 2017-11-09 15:25:45 -08:00
_redirects Move kubectl ref docs to /docs/reference/. (#6472) 2017-11-28 18:02:16 -08:00
editdocs.md update website 2017-10-19 16:43:08 +08:00
google2b743c61aa37ebbe.html
google3a25d10f6aadcdc0.html
googlea92cf511a27d4f6b.html
googlead862a0628bec321.html
googlebea0044df4aa3179.html
googlece48a67808b497a5.html
index.html Updates to Partner Page and Kubecon Banners 2017-11-24 11:35:15 +11:00
jquery-ui.html
labels.yaml
netlify.toml
netlify_noindex_headers.txt
robots.txt
skip_title_check.txt Remove pod-termination doc (#6199) 2017-11-07 16:29:05 -08:00
skip_toc_check.txt Remove pod-termination doc (#6199) 2017-11-07 16:29:05 -08:00
update-imported-docs.sh Release 1.8 (#5659) 2017-09-28 21:46:51 -07:00
verify-docs-format.sh

README.md

Instructions for Contributing to the Kubernetes Documentation

Welcome! We are very pleased you want to contribute to the Kubernetes documentation.

You can click the Fork button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.

Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer. Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a Kubernetes tech reviewer when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.

For more information about contributing to the Kubernetes documentation, see:

Thank you!

Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation!