The dockershim is being depreciated in k8s 1.23 and is being removed from the kubelet. Time frame for this occurring is 1.24.

What this means for WMCO/OpenShift, is that when WMCO ships with the 1.23 kubelet in OpenShift 4.10, Windows nodes will not function unless containerd is installed on the underlying Windows instance. To deal with this we should be building containerd and shipping it as part of the payload.
This will especially be beneficial as it would allow us to dictate the containerd version used by our customers to ensure compatibility with our product.

Engineering Details:
[I found this blog from James sturtevant|https://www.jamessturtevant.com/posts/Windows-Containers-on-Windows-10-without-Docker-using-Containerd/
]:so it doesnt look like theres a Windows module way to install containerd like there was Docker.

Unable to find source-code formatter for language: powershell. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yamlInstall-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider

There are currently no Windows AMIs with containerd installed available on AWS.

Containerd will have to be forked in OpenShift/containerd and added as a submodule for WMCO repo.

Acceptance criteria:

• Customer facing documentation needs to state that installing Docker or using a Windows VM image with Docker installed is no longer necessary.
• Windows instances configured by WMCO have containerd installed and running.