Go to file
Rajesh Deshpande d3cd85d496 Correcting API version in example (#13670)
API version of KubeSchedulerConfiguration is corrected to kubescheduler.config.k8s.io
2019-04-08 18:15:07 -07:00
.github Fix#13372 - Issue template for bug, support, feature requests (#13373) 2019-04-02 08:02:38 -07:00
archetypes Convert site to Hugo (#8316) 2018-05-05 09:00:51 -07:00
content Correcting API version in example (#13670) 2019-04-08 18:15:07 -07:00
data Official 1.14 Release Docs (#13174) 2019-03-25 15:06:16 -07:00
functions-src Add header-checking function (#9880) 2018-10-03 13:04:39 -07:00
i18n Init Spanish translation (#13543) 2019-04-04 13:11:20 -07:00
layouts Fix#13372 - Issue template for bug, support, feature requests (#13373) 2019-04-02 08:02:38 -07:00
sass Fix #12506 - Misalignment of the community logos (#12507) 2019-03-19 13:56:22 -07:00
scripts Add a script util to check if a file is modified by an open PR (#12790) 2019-04-04 03:08:49 -07:00
static add Nokia case study (#13676) 2019-04-08 15:14:27 -07:00
update-imported-docs Reference documentation for kube components (#13444) 2019-03-27 15:58:19 +08:00
.dockerignore Prevent to send all files to docker daemon (#10129) 2018-08-30 06:25:07 -07:00
.editorconfig Add editorconfig (#11551) 2019-01-28 11:32:42 -08:00
.gitignore Add editorconfig (#11551) 2019-01-28 11:32:42 -08:00
.travis.yml travis performance improvement (#13304) 2019-03-20 15:57:08 -07:00
CONTRIBUTING.md Use CoCC email for reporting CoC violations (#10621) 2018-10-15 16:33:34 -07:00
Dockerfile Fix ##12434 - Empty continuation line warning while building docker image (#12435) 2019-02-01 10:06:45 -08:00
LICENSE fix a series punctuation errors 2016-12-22 11:24:05 +08:00
Makefile Remove --ignoreCache flag (#13133) 2019-03-14 06:52:26 -07:00
OWNERS Add milestone team, clean up others teams (#13287) 2019-03-20 13:47:01 -07:00
OWNERS_ALIASES rename sieben to remyleone (#13690) 2019-04-08 17:57:04 -07:00
README-de.md Fixed typo in German README (#13550) 2019-04-01 09:24:34 -07:00
README-es.md Init Spanish translation (#13543) 2019-04-04 13:11:20 -07:00
README-fr.md Init French translation (#12548) 2019-02-13 09:29:21 -08:00
README-ko.md Update website link in Readme and badges to readme (Korean) for consistency (#12682) 2019-02-28 05:41:27 -08:00
README.md Update website link in Readme and badges to readme (Korean) for consistency (#12682) 2019-02-28 05:41:27 -08:00
SECURITY_CONTACTS Update embargo doc link in SECURITY_CONTACTS and change PST to PSC (#13041) 2019-03-20 08:47:17 -07:00
code-of-conduct.md Add the code of conduct (#11919) 2019-02-04 15:31:57 -08:00
config.toml Init Spanish translation (#13543) 2019-04-04 13:11:20 -07:00
labels.yaml Issue #124: Automatically create labels. 2016-08-04 22:57:44 -07:00
netlify.toml Update to Hugo 0.53 and remove all .Site references (#12079) 2019-02-05 08:33:23 -08:00
package.json Add header-checking function (#9880) 2018-10-03 13:04:39 -07:00

README.md

The Kubernetes documentation

Build Status GitHub release

Welcome! This repository houses all of the assets required to build the Kubernetes website and documentation. We're very pleased that you want to contribute!

Contributing to the docs

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. This copy is 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:

README.md's Localizing Kubernetes Documentation

Korean

See translation of README.md and more detail guidance for Korean contributors on the Korean README page.

You can reach the maintainers of Korean localization at:

Running the site locally using Docker

The recommended way to run the Kubernetes website locally is to run a specialized Docker image that includes the Hugo static site generator.

If you are running on Windows, you'll need a few more tools which you can install with Chocolatey. choco install make

If you'd prefer to run the website locally without Docker, see Running the site locally using Hugo below.

If you have Docker up and running, build the kubernetes-hugo Docker image locally:

make docker-image

Once the image has been built, you can run the site locally:

make docker-serve

Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.

Running the site locally using Hugo

See the official Hugo documentation for Hugo installation instructions. Make sure to install the Hugo version specified by the HUGO_VERSION environment variable in the netlify.toml file.

To run the site locally when you have Hugo installed:

make serve

This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

Thank you!

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