c3b684f9b6
here is my test result:
[root@localhost ~]# sh -c 'for i in {1..100}; do sleep 1; if dig www.baidu.com;then exit 0; fi; exit 1'
sh: -c: line 1: syntax error: unexpected end of file
[root@localhost ~]# sh -c 'for i in {1..100}; do sleep 1; if dig www.baidu.com;then exit 0; fi;done; exit 1'
; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7 <<>> www.baidu.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27927
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.baidu.com. IN A
;; ANSWER SECTION:
www.baidu.com. 1125 IN CNAME www.a.shifen.com.
www.a.shifen.com. 106 IN A 180.97.33.107
www.a.shifen.com. 106 IN A 180.97.33.108
;; Query time: 16 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Fri Oct 27 02:42:38 EDT 2017
;; MSG SIZE rcvd: 101
[root@localhost ~]# echo $?
0
[root@localhost ~]#
|
||
|---|---|---|
| .github | ||
| _data | ||
| _includes | ||
| _layouts | ||
| _sass | ||
| case-studies | ||
| cn | ||
| community | ||
| css | ||
| docs | ||
| images | ||
| js | ||
| partners | ||
| staging-container | ||
| test | ||
| .gitignore | ||
| .travis.yml | ||
| 404.md | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| _config.yml | ||
| _redirects | ||
| 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 | ||
| update-imported-docs.sh | ||
| 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!