Go to file
António Meireles bb29bc897d missing 'kubelet config annotate-cri' phase on additional controller nodes (#10598)
Hi all,

AFAICT and after reading
[this](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-alpha/)
`kubeadm alpha phase kubelet config annotate-cri` should invoked for
consistency in all joining controller nodes (to match what is already
done by default in the seed/initial one).

best regards,

António

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
2018-10-14 17:36:16 -07:00
.github Update PR template for 1.13 release (#10603) 2018-10-12 18:00:20 -07:00
archetypes
content missing 'kubelet config annotate-cri' phase on additional controller nodes (#10598) 2018-10-14 17:36:16 -07:00
data
functions-src
i18n
layouts Update localization guidelines (#10485) 2018-10-12 14:25:01 -07:00
resources/_gen/assets/sass
sass
scripts
static
update-imported-docs
.dockerignore
.gitignore
.travis.yml
CONTRIBUTING.md
Dockerfile Update README instructions and Docker image (#10537) 2018-10-09 18:08:28 -07:00
LICENSE
Makefile
OWNERS
OWNERS_ALIASES Update localization guidelines (#10485) 2018-10-12 14:25:01 -07:00
README.md Update README instructions and Docker image (#10537) 2018-10-09 18:08:28 -07:00
SECURITY_CONTACTS
config.toml Fix Hugo config.toml as valid (#10605) 2018-10-12 18:16:50 -07:00
labels.yaml
netlify.toml
package.json

README.md

The Kubernetes documentation

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:

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'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.

Thank you!

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