911ecf5c76
* Add link for IBM Cloud Private-CE on Linux Containers project IBM Cloud Private-CE (Community Edition) on Linux Containers is a Terraform/Packer/BASH based IaC to create a seven node (1 Boot, 1 Master, 1 Management, 1 Proxy and 3 Workers) LXD cluster on Linux Host. Supported versions are: ICP 2.1.0.1 + Kubernetes 1.8.3 and ICP 2.1.0.2 + Kubernetes 1.9.1 Goal of this project was to create a Terraform based solution that can be easily configured to meet user needs for development purposes. This IaC script can be applied to Local or Cloud based Linux Host (Ubuntu). Additionally, environment specific TFVARS can allow simpler integration with DevOps pipeline. Detailed information can be found at https://github.com/HSBawa/icp-ce-on-linux-containers. * Update verbiage to expand IaC |
||
|---|---|---|
| .github | ||
| _data | ||
| _includes | ||
| _layouts | ||
| _plugins | ||
| _sass | ||
| case-studies | ||
| cn | ||
| community | ||
| css | ||
| docs | ||
| images | ||
| js | ||
| partners | ||
| staging-container | ||
| test | ||
| update-imported-docs | ||
| .gitignore | ||
| .travis.yml | ||
| 404.md | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| _config.yml | ||
| _redirects | ||
| code-of-conduct.md | ||
| editdocs.md | ||
| google2b743c61aa37ebbe.html | ||
| google3a25d10f6aadcdc0.html | ||
| googlea92cf511a27d4f6b.html | ||
| googlead862a0628bec321.html | ||
| googlebea0044df4aa3179.html | ||
| googlece48a67808b497a5.html | ||
| index.html | ||
| jquery-ui.html | ||
| labels.yaml | ||
| netlify.toml | ||
| netlify_noindex_headers.txt | ||
| robots.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:
- Contributing to the Kubernetes Documentation
- Creating a Documentation Pull Request
- Writing a New Topic
- Review Issues
- Staging Your Documentation Changes
- Using Page Templates
- Documentation Style Guide
Thank you!
Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation!