Add known issue for WSL2 and cgroupv2 support

This adds a note to the Known Issues document with details related to
proper setup requirements for cgroupv2 support and links to the known
issues page for extra visibility from the Using WSL2 page.

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

Author: stmcginnis

site/content/docs/user/known-issues.md

@@ -40,6 +40,7 @@ description: |-
 * [Failed to get rootfs info](#failed-to-get-rootfs-info--stat-failed-on-dev)
 * [Docker Desktop for macOS and Windows](#docker-desktop-for-macos-and-windows)
 * [Older Linux Distributions](#older-linux-distributions)
+* [Failure to Create Cluster on WSL2](#failure-to-create-cluster-on-wsl2)
 
 ## Troubleshooting Kind
 
@@ -376,7 +377,14 @@ Although the policy has been fixed in Fedora 34, the fix has not been backported
 
 ## Docker Desktop for macOS and Windows
 
-Docker containers cannot be executed natively on macOS and Windows, therefore Docker Desktop runs them in a Linux VM. As a consequence, the container networks are not exposed to the host and you cannot reach the kind nodes via IP. You can work around this limitation by configuring [extra port mappings](https://kind.sigs.k8s.io/docs/user/configuration/#extra-port-mappings) though.
+Docker containers cannot be executed natively on macOS and Windows, therefore
+Docker Desktop runs them in a Linux VM. As a consequence, the container networks
+are not exposed to the host and you cannot reach the kind nodes via IP.
+
+You may be able to work around this limitation by configuring [extra port
+mappings](https://kind.sigs.k8s.io/docs/user/configuration/#extra-port-mappings),
+leveraging [cloud-provider-kind](https://github.com/kubernetes-sigs/cloud-provider-kind),
+using a network proxy, or other solution specific to your environment.
 
 ## Older Linux Distributions
 
@@ -393,6 +401,21 @@ Command Output: WARNING: Your kernel does not support cgroup namespaces.  Cgroup
 Using KIND in these environments will require upgrading your OS to a more recent version that supports cgroup namespaces.
 Another option is to run a virtual machine using a newer kernel.
 
+## Failure to Create Cluster on WSL2
+
+Some Linux kernel options for WSL2 do not have cgroup configured in a way that
+KIND and other Linux-focused tools may expect. This may result in a failure
+message when attempting to create a cluster, similar to:
+
+```txt
+unable to start container process: error adding pid 655569 to cgroups
+```
+
+The KIND development team is not able to provide support with Windows and WSL, so
+the project relies on community support and feedback. It has been noted that the
+steps detailed in [https://github.com/spurin/wsl-cgroupsv2](https://github.com/spurin/wsl-cgroupsv2)
+have been necessary to resolve this issue.
+
 [kind#156]: https://github.com/kubernetes-sigs/kind/issues/156
 [kind#229]: https://github.com/kubernetes-sigs/kind/issues/229
 [kind#1179]: https://github.com/kubernetes-sigs/kind/issues/1179

site/content/docs/user/using-wsl2.md

@@ -11,9 +11,10 @@ description: |-
   All the tools needed to build or run kind work in WSL2, but some extra steps are needed to switch to WSL2. This page covers these steps in brief but also links to the official documentation if you would like more details.
 ---
 
-## Getting Windows 10
+## Getting Windows 10 or 11
 
-Download the latest ISO at https://www.microsoft.com/en-us/software-download/windows10ISO. Choose "Windows 10 May 2020 Update". If there's a later update, that will work too.
+Download the latest ISO at https://www.microsoft.com/en-us/software-download/.
+Choose the latest Windows 10 or Windows 11 release.
 
 ### Installing on a virtual machine
 
@@ -63,13 +64,11 @@ wsl --set-default-version 2
 
 Install Docker with WSL2 backend here: https://docs.docker.com/docker-for-windows/wsl/
 
-
 ## Setting up Docker in WSL2 without Docker Desktop
 
 Alternatively, docker can be installed in WSL2 without using Docker Desktop.
 See for example: https://dev.to/bowmanjd/install-docker-on-windows-wsl-without-docker-desktop-34m9
 
-
 Now, move on to the [Quick Start](/docs/user/quick-start) to set up your cluster with kind.
 
 ## Accessing a Kubernetes Service running in WSL2
@@ -141,3 +140,4 @@ kernel=c:\\path\\to\\your\\kernel\\bzImage
 - You can check the status of all installed distros with `wsl --list --verbose`.
 - If you had a distro installed with WSL1, you can convert it to WSL2 with `wsl --set-version <distro> 2`
 - Alternative of [Accessing a Kubernetes Service running in WSL2](#accessing-a-kubernetes-service-running-in-wsl2) or [Setting Up An Ingress Controller](/docs/user/ingress/#setting-up-an-ingress-controller) for accessing workloads is using `kubectl port-forward --address=0.0.0.0`.
+- See the [Known Issues](/docs/user/known-issues/) page for additional Windows-related issues and concerns.