kubeadm: adapt docs for 1.24 and dockershim removal

[neolit123]

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.
• 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.

xref kubernetes/kubeadm#2626

[neolit123]

/sig cluster-lifecycle
/hold
until kubernetes/kubernetes#107317 merges

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

🔨 Explore the source changes: 3184c22

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/61f026fa64c005000873e1e9

[neolit123]

/sig windows
for content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md

[netlify]

✔️ Deploy Preview for kubernetes-io-main-staging ready!

🔨 Explore the source changes: 83c9408

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/61df04191c0650000769094a

😎 Browse the preview: https://deploy-preview-31309--kubernetes-io-main-staging.netlify.app

[neolit123]

/cc @SataQiu @pacoxu

[neolit123]

pushed updates:

• use "Docker Engine" as the container-runtime name (instead of "docker" or "Docker")
• add note that explains briefly what cri-dockerd is and that it is a new project

[sftim]

LGTM

A couple of concerns about changes not linked to the dockershim removal. Just in case we need to revert this change, I'd prefer to have those changes in their own commit. Ideally: a different PR, that targets the appropriate branch (possible main).

[sftim]

nit: avoid calling things “new” (it creates a follow-up task to reword for the next release).
Maybe “If you're using Kubernetes v1.24 or newer, ”

[neolit123]

reworded to:

{{< note >}}
Docker Engine does not implement the [CRI](/docs/concepts/architecture/cri/)
which is a requirement for a container runtime to work with Kubernetes.
For that reason, an additional service [cri-dockerd](https://github.com/Mirantis/cri-dockerd)
has to be installed. cri-dockerd is a project based on the legacy built-in
Docker Engine support that was [removed](/dockershim) from the kubelet in version 1.24.
{{< /note >}}

[sftim]

LGTM

I'm not confident about signing off the Windows-specific changes; the other parts look good.

[neolit123]

@sftim updated.

/cc @marosset
PTAL for /lgtm on the kubeadm / Windows changes.
followups can be done in #31395

[marosset]

/lgtm
For Windows changes.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 36c334d65f901c54dda03eaee5703cf2b0baf9b8

[sftim]

BTW, this links to a page stating that

Customers who want to install a container runtime on Windows server are encouraged to transition to either containerd, Moby, or the Mirantis Container Runtime.

Not sure what we should cover. Maybe we should advise readers to install one of those 3 things and then continue? We can cite those as Microsoft's suggested runtimes for Windows servers.
I think cri-dockerd will work with Moby (Docker Engine without the trademarks) but I'm not sure - I don't actually use Docker very much.

[neolit123]

i'm not familiar with the Mirantis product line.

follow ups related to Windows nodes can be tracked in:
#31395

[sftim]

TBH I think we need a separate issue. #31395 has a specific focus.

@marosset - would you be willing to open a new issue to track any concerns you have about the Windows aspects of setup? (if you don't have any concerns, no need to act)

[sftim]

Let's merge this. It makes the pages much better, even if there's room for more improvement.
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jihoon-seo]

• Related issue: Action on Docker mentions in Tasks > Administer Cluster #30970