/docs/tasks/tools/install-kubectl/ is redirected to
/docs/tasks/tools/
This commit replace the redirect links for installing kubectl
with direct links.
This commit fixes the packages not found error during
Docker installation. The packages containerd.io 1.2.13-2,
docker-ce 19.03.11, and docker-cs-cli 19.03.11 are currently not in
Ubuntu 20.10. This commit instead points users to validated
versions of Docker.
fixes https://github.com/kubernetes/kubernetes/issues/99831
Signed-off-by: Enyinna Ochulor <eochulor@vmware.com>
This simplifies the containerd installation instructions. All Linux distros will
now download from Docker repos, including Ubuntu 18.04 which previously
installed from Ubuntu repos.
The Docker runtime instructions have also been simplified. The RHEL/CentOS
specific option overlay2.override_kernel_check=true option has been removed.
It seems Docker will now autodetect overlay2 support on older Linux kernels
<4.0.0,>=3.10.0-514, which have back-ported overlay2 support on RHEL/CentOS 7.4+
See moby/moby#34368
The use of `apt-key` to install has also been removed as it is now deprecated
and will be last available in Debian 11 and Ubuntu 22.04.
Also updates the Docker repository setup instructions in container-runtimes.md,
to now refer to the respective instructions at https://docs.docker.com/engine/install/
which has already made the move to use the signed-by option.
/docs/reference/setup-tools/kubeadm/kubeadm/ is redirected to
/docs/reference/setup-tools/kubeadm/
This replaces the redirect links of kubeadm with the direct links.
- Add the new page "Configuring a cgroup driver"
The page includes details on how to configure the cgroup driver
using kubeadm. It also includes a migration guide for users to
move to the "systemd" driver.
- Link to the new page from install-kubeadm.md and container-runtimes.md
This page listed `/var/run/docker.sock` as the UNIX domain socket path for the Docker container runtime, but it's actually `/var/run/dockershim.sock`, as the kubelet documentation indicates as the default value for the `--container-runtime-endpoint` argument:
https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/
The socket file specified (`/var/run/docker.sock`) is where the Docker daemon listens for requests for the Docker API, not the CRI interface.
This commit adds a cosmetic change by adding backticks to show the env
var in monospace font when rendered.
Mention Flatcar Linux in kubeadm troubleshooting doc, alongwith Fedora
CoreOS.
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
Unless that first part of the paragraph is meant to be more like a subheading (in which case it could use some reformatting), I would like to suggest a minor rephrase so that it becomes a proper sentence and has a predicate.
Thanks for considering this!
This patch updates the CRI-O documentation to the latest available
version. It also adds a dedicated cgroup driver section to mention that
the configuration has to be in sync.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Add containerd installation on Debian
write docker keyring in a seprate file
Co-authored-by: Tim Bannister <tim@scalefactory.com>
edit comment
Co-authored-by: Tim Bannister <tim@scalefactory.com>
remove sudo
Co-authored-by: Tim Bannister <tim@scalefactory.com>
There is no need to restart the kubelet as part of configuring kubeadm to set the cgroup driver. At this point in the setup instructions, the kubernetes cluster isn't even up and running yet, as kubeadm init hasn't been run. The previous step even says the kubelet is in a crashloop waiting for kubeadm.
The "Set up the Docker daemon" step fails because the initial files have not been created. I copied the step of creating of the /etc/docker/ folder from the CentOS/RHEL instructions to the Ubuntu Instructions
For someone following the guide to setup a cluster, sudo is being used in the initial commands, I think it would great to carry this on till the last commands.
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 existing page had lots of references to specific products. Those
references aren't in line with the current content guide, so I cut them
out.
I then reshaped the page to be a general set of advice about managing
and running large clusters.
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
* 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).