Go to file
Qiming b5f6df9926 Consolidate YAML files [part-8] (#9347)
* Consolidate YAML files [part-8]

This PR exacts the YAML files referenced from the following subdirs:

- docs/concepts/workloads
- docs/concepts/configuration
- docs/concepts/policy

The following problems are fixed:

- docs/concepts/workloads/controllers/ doesnt have a 'cronjob.yaml for
  test
- the exactly same `pod.yaml` was used in both the task/config-pod-container
  topic and the concepts/configuration topics.

* Update examples_test.go

* Add missing yaml file.
2018-07-02 17:35:20 -07:00
.github Update pull request template (#9311) 2018-06-29 10:53:21 -07:00
archetypes
content Consolidate YAML files [part-8] (#9347) 2018-07-02 17:35:20 -07:00
data Fix broken links to /admin/multiple-zones (#9193) 2018-06-25 22:18:52 -07:00
layouts Add Git info to per-page template (#9309) 2018-07-02 16:17:19 -07:00
src/sass [css] Remove bullet styling from "tab-nav" components. (#9020) 2018-06-15 13:42:28 -07:00
staging-container
static Add Git info to per-page template (#9309) 2018-07-02 16:17:19 -07:00
test Consolidate YAML files [part-8] (#9347) 2018-07-02 17:35:20 -07:00
update-imported-docs Add release notes for 1.11 (#9287) 2018-06-27 17:13:46 -07:00
.gitignore
.travis.yml Set up examples gate job for 1.11 (#9345) 2018-07-02 12:53:18 -07:00
CONTRIBUTING.md
Dockerfile Add Docker build capability (#9128) 2018-06-21 10:13:29 -07:00
LICENSE
Makefile Add Docker build capability (#9128) 2018-06-21 10:13:29 -07:00
OWNERS Add two new reviewers (#9090) 2018-06-19 08:24:34 -07:00
OWNERS_ALIASES Overall cleanup for kubeadm setup guide. (#8981) 2018-06-13 11:23:29 -07:00
README.md Add Docker build capability (#9128) 2018-06-21 10:13:29 -07:00
SECURITY_CONTACTS Add a SECURITY_CONTACTS file (#8824) 2018-06-06 14:37:23 -07:00
config.toml Add Git info to per-page template (#9309) 2018-07-02 16:17:19 -07:00
labels.yaml
netlify.toml Add Git info to per-page template (#9309) 2018-07-02 16:17:19 -07:00
netlify_noindex_headers.txt
skip_title_check.txt
skip_toc_check.txt
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:

Building the site using Docker

If you'd like, you can build the Kubernetes docs using Docker. To get started, build the image locally:

$ make docker-image

# The underlying command:
$ docker build . \
  --tag kubernetes-hugo \
  --build-arg HUGO_VERSION=0.40.3

You can create an image for a different version of Hugo by changing the value of the HUGO_VERSION argument for the build. You must specify a version or the image will not build. Once the kubernetes-hugo image has been built locally, you can build the site:

$ make docker-serve

# The underlying command:
$ docker run \
  --rm \
  --interactive \
  --tty \
  --volume $(PWD):/src \
  kubernetes-hugo:latest \
  hugo

As when building without using a Docker container, the results of the build will be published to the public directory (the default output directory for Hugo, the static site generator used to build this site).

Thank you!

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