The current command on line 125 throws a permission error. The sudo elevation of rights applies to the containerd command, not the write (>) to a file owned by root.
This is the command as copied from the current page:
student@master:~$ sudo containerd config default > /etc/containerd/config.toml
-bash: /etc/containerd/config.toml: Permission denied
Instead leverage sudo tee. It works and no more error:
student@master:~$ containerd config default | sudo tee /etc/containerd/config.toml
fixing content in tabs on adding-windows-nodes.md
reworking tabbed content on adding-windows-nodes.md
intro-windows-in-kubernetes.md
Updating Windows pause image details
PR feedback for adding-windows-nodes.md
Updating comments got GMSA on containerD
kubelet can fail to start due to various reason, e.g mismatching cgroup
drivers. Add this step to save user from having to go back and check when
found etcd cluster is not running successfully.
The command resided under "kubeadm alpha certs".
It will be promoted to GA in 1.20 as "kubeadm certs".
The existing command "kubeadm alpha" will
remain present for one more release, but it will be hidden
from documentation as it is deprecated.
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
Anna Jung (VMware)