Tim Bannister
c5abd7704a
- Use glossary shortcodes in Node concept Add glossary tooltips to help new readers take in unfamiliar concepts. - Move minion hint to glossary The page about Node need not mention the former name (minion): it has been many releases since the name change. Instead, add a hint to the full glossary definition. - Use note shortcodes where appropriate - Order node management section first in concept page - Drop list of components that act on Nodes With Operators and CustomResourceDefinitions now common, plus the cluster API, it's less easy to give a definitive list of components that interacr with Node objects. - Tidy old mentions of GA features for Node - Give node tainting by condition its own section - Introduce toleration concept before using it - Mention version in TopologyManager feature state - Other rewording - Tidy Node condition table - Explain SchedulingDisabled synthesized condition - Drop details of supported versions for NodeRestriction Assume that cluster version is v1.13 or later
The Kubernetes documentation
Welcome! This repository houses all of the assets required to build the Kubernetes website and documentation. We're glad 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 initially 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:
- Start contributing
- Staging Your Documentation Changes
- Using Page Templates
- Documentation Style Guide
- Localizing Kubernetes Documentation
Localization README.md's
Running the website locally using Docker
The recommended way to run the Kubernetes website locally is to run a specialized Docker image that includes the Hugo static website 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 website 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 website locally:
make docker-serve
Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
Running the website locally using Hugo
See the official Hugo documentation for Hugo installation instructions. Make sure to install the Hugo extended version specified by the HUGO_VERSION environment variable in the netlify.toml file.
To run the website 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 website. As you make changes to the source files, Hugo updates the website 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 appreciate your contributions to our website and our documentation!