The Debian tool, APT, lets you write GPG keyrings into a file per
trusted source, inside /etc/apt/trusted.gpg.d
Recommend that approach, as it is easier to manage.
- Reword page introduction.
- Match headings to contents; before, headings were sometimes followed
first by unrelated text and then, with no clear divider, text that did
not relate to the heading.
- Remove Fracti link (not in line with content guide).
Updating the syntax on redirection to repo files in Ubuntu as in Debian documentation, since the syntax requires privileges to perform the redirection, removing double quotes from apt Sources files, to avoid issues with apt while reading source packages.
systemd_cgroup = true in plugins."io.containerd.grpc.v1.cri" is no longer
supported by containerd 1.3.x. Enabling it causes containerd to skip loading
the cri plugin.
Add the preferred setting to the container runtime configuration documentation.
Ref: https://github.com/containerd/containerd/issues/4574
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
- Add link from the kubeadm-config page to the paragraphs on
using "--config" with "init" and "join".
- Improve text in the the paragraphs on using "--config" with
"init" and "join".
- Reword the link about the configuration file in the
create-cluster-kubeadm page.
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
clearbjli
Arhell
Michael Hofer
Neha Viswanathan
Kubernetes Prow Robot
Tim Bannister
Reymer Vargas
Mikko Ylinen
Lubomir I. Ivanov
Pratik raj
Yoon
Qiming Teng
Dennis Schridde
Maxime Guyot
RA489
Hannes Leutloff
Thomas Tanaka
Jubayer Abdullah Joy
tallaxes
Savitha Raghunathan
Ricardo Pchevuzinske Katz
wangxy518
Peter Hunt
M. Habib Rosyad
Anna Jung
TAKAHASHI Shuuji
Evgeny Shmarnev
inductor