Added sudo uniformly everywhere it required as it presence doesn't affect anything , but it help new user's of linux , docker or kubernetes who are not much familiar with internals and also for who doesn't read the documentation line by line and use the guides for command reference and just copy paste for their use.
Also , changed the way of writing or creating files , now using "tee" because previous way gives permission issue for non sudo users.
This replaces the word "master" with "control-plane node" in order to use
more inclusive language.
Also uses consistent wording / spelling in this context.
References: #21621
Suggested-by: Lubomir I. Ivanov <lubomirivanov@vmware.com>
It was not clear to me that I had to add the unit file to all nodes and restart the kubelet service. I was stuck wondering why etcd could not connect to the other peers until i realized that kubelet was only running on `HOST-0`.
Remove parantheses.
Improve phrasing.
Update content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Remove on-premises VMs section
* Remove CloudStack page
This page does not fit in with current content guidelines.
* Remove DC/OS page
This page does not fit in with current content guidelines.
* Remove oVirt page
This page does not fit in with current content guidelines.
* Remove empty section: On-Premises VMs
Signed-off-by: Jubayer Abdullah Joy <jubayerjoy98@gmail.com>
- Changed filesystem paths to monospace in `/docs/setup/learning-environment/minikube.md` mounted host folder section
* Revise Pod concept
Adapt the existing Pod documentation to suit the Docsy theme, by
promoting the Pod concept itself to /docs/concepts/workloads/pods/
Following on from this, update the Pod Lifecycle page to cover the
lifecycle of a Pod and follow on directly from the Pod concept,
for readers keen to understand things in detail.
This change also removes the automatic contents list from the Pod
overview page. Instead, the new page links to all the pages
inside the Pod section.
* Update links to Pod concept
Link to updated content
* Incorporate Pod concept suggestions
Co-authored-by: Celeste Horgan <celeste@cncf.io>
* Revise StatefulSet suggestion for Pod concept
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Kubeadm should be CNI agnostic and should not define what is
considered a popular CNI plugin and what isn't.
- Remove the tabs that list CNIs such as Calico, WeaveNet, etc.
- Preserve the note that Calico is currently the only CNI
kubeadm e2e tests are run against.
- Change the link to enumerate CNIs to:
/docs/concepts/cluster-administration/networking/
This is in prep for link checker. By using inline links everywhere, we:
- reduce the risk of dangling, missing, unused links as you can see from the PR;
- simplify the link checker logic (under development).