* Docs to change Container runtime
* Updated header
* Updated header
* Few changes made according to the reviews
* Updated few headings
* Updated few markdown changes
* Reverted a unwanted changes
* Removed the double extension in the filename
* Updated
* Updated according to review
* Final Updates
* Added instructions to remove docker engine
* Minor changes
* Minor updates on heading
* Minor updates on lists
* Minor updates on line 106
* Minor updates on line 106
This PR fixes two problems in the cascading deletion page:
- The indentation of list items should be 2 spaces for unordered lists,
or 3 spaces for ordered lists. We should avoid using 4 spaces as
indentation because 4-spaces indentation has special meaning in
markdown.
- The garbage-collection page was moved to a new place. With redirect
records for English site, there seems no obvious problems. However,
for localization teams, such redirection records don't exist. It is
super easy to create a dangling link in localized pages.
This change is to update the documentation for reserved-memory flag.
Now, for specifying memory reservations across multiple NUMA nodes,
semicolon needs to be used as separator.
Signed-off-by: Ravindra Thakur <ravindra.nath.thakur@est.tech>
The command "kubeadm kubeconfig user" is missing
some examples and more details on why it is needed.
- Add a new section "Generating kubeconfig files
for additional users" under the kubeadm-certs page.
- Link to this section from the kubeadm-kubeconfig reference page.
- Link to this section from the create-cluster-kubeadm page.
Sysbox is an open-source container runtime (similar to "runc") that supports
running VM-workloads such as Docker and Kubernetes inside unprivileged
containers or pods.
Sysbox containers always use the Linux user-namespace for isolation, plus
specially crafted proc and sys filesystems, some syscall interception,
filesystem ID-mapping, and more.
It's possible to run Kubernetes, K3s, K0s, inside containers or pods deployed
with Sysbox. This commit aims to make the Kubernetes community aware of this
option.
Signed-off-by: Cesar Talledo <ctalledo@nestybox.com>
Touch the following files:
- Implementation details: remove docker specifics, which is changing
in 1.24
- Create cluster: small language cleanup, remove note about 1.24
- Install kubeadm: Include two up-to-date tables for Linux / Windows
with known endpoints. Include cri-dockerd.
- Kubelet integration: (side cleanup) use "container runtime" instead of
"CRI runtime" (which is incorrect). Mention that only updating
"--container-runtime-endpoint=.." is required if the user wishes
to override the CR on a certain host. Dockershim->CR-foo migration
guides would make the "--container-runtime=remote" flag explicit
and we want to remove it at some point.
- Troubleshooting kubeadm: Remove some instances of Docker troubleshooting
that imply docker as default CR, or talk about old Docker versions.
Be more generic about container runtimes.
- Adding Windows nodes: move the containerd tab before the Docker
tab, as containerd is now the default. Remove note about being explicit
about --cri-socket. Add note that crictl is required for both
Docker and containerd. Add note that cri-dockerd is required if
the user wants to use Docker EE on Windows.
The current entry under additional information about drain can
be confusing and users might jump into draining the nodes before
the upgrade steps (as a pre-req), following the
instructions in the external link. This is not accurate.
Adjust the entry text to explain that drain is a step as part of
the upgrade process and this additional information entry just
mentions why it is needed.
This commit reformats the memory manager page:
- convert the page from DOS to UNIX format;
- wrap long lines where appropriate for ease of change tracking;
- remove useless trailing spaces and empty lines.
This commit contains **NO** changes to the text itself.
This PR fixes the memory manager page by:
- removing links to non-existent sections;
- fixing links with bad anchors;
- fixing incorrect language tag for code snippets
Revise tasks within “Manage Memory, CPU, and API Resources”:
- reword to avoid implying that API clients can create a container
(you can, but its done by creating a Pod)
- call a manifest a manifest
- use tooltips where relevant
- link to new API reference not the old one
- other improvements
* Update kubeadm-upgrade.md
`apt-mark hold` is still required when `apt-get` is used with `--allow-change-held-packages`.
`--allow-change-held-packages` unholds the package but it doesn't pin the new version.
* Add missing changes
* Update kubeadm-upgrade.md
Remove apt >1.1 examples.
* Update docs to clarify the dns configmap format.
* Update content/en/docs/tasks/administer-cluster/nodelocaldns.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Kubernetes Prow Robot