* Link upgrade to skewed version page
It provides the order of upgrade and shows which versions are supported.
Solves (at least partially ) #14420
* Update cluster-management.md
* Update cluster-management.md
* document pod downwardAPI fieldRef & resourceRef values of en version
* document pod downwardAPI fieldRef & resourceRef values of zh version
* typo correction
* Correcting minikube quickstart steps
In minikube quickstart section , it was difficult to differentiate between command and its output. Also, There was no details given for each steps and its expected output. This PR fixes these issues.
* Correcting number formatting
Correcting number formatting
* Correcting numbering
Correcting numbering
* Update content/en/docs/setup/minikube.md
Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>
* Update content/en/docs/setup/minikube.md
Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>
* Update content/en/docs/setup/minikube.md
Co-Authored-By: Franklin Yu <franklinyu@hotmail.com>
* Corrected formatting
Corrected formatting
* Correcting number sequence
Correcting number sequence
* Updated Linux Academy courses
* Apply suggestions from code review
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Fix link syntax
* Update overview.md
Both local and pod port number are same i.e. 6379 which causes confusion to first time reader. This can be easily avoided by using two different port number.
* Correcting order of display for daemon set tasks
Correcting order of display for daemon set tasks
* Correcting display order of daemon set task
Correcting display order of daemon set task
here apt installs both kubelet and kubectl but just holds kubelet. I think kubectl should alse be held by apt-mark.
```
# replace x in 1.14.x-00 with the latest patch version
apt-mark unhold kubelet && \
apt-get update && apt-get install -y kubelet=1.14.x-00 kubectl=1.14.x-00 && \
apt-mark hold kubelet
```
Add meeting guidelines, graphic
Update embedded image
Use raw HTML for image link
Edit path
Indent list items
minor edits
Add line breaks for indentation
Add bolding
Add section for meetings
Feedback from jimangel
* Use glossary references where appropriate
* Link from Pod overview to detailed Pod concept
* Assume that privileged containers are stable
* Improve wording
* Write Pod in upper case
As Pod is an API object, write it in upper case.
好风