<p>I'm running a cluster with kind - one worker node.</p>
<p>However when I do <code>kubectl get nodes</code> I can't see the node, but instead I see 'kind control plane' - which makes no sense to me, control plane is a node??</p>
<p>The worker node must be running, because I can do <code>kubectl exec --stdin --tty &lt;name of the pod&gt; /bin/sh</code> and see inside of the container that's running my app.</p>
<p>Is this some weird WSL2 interaction? Or I'm simply doing something wrong?</p>

LemonadeJoe
<p><code>control-plane</code> is just a name.  If you just run <code>kind create cluster</code>, its <a href="https://kind.sigs.k8s.io/docs/user/configuration/#nodes" rel="nofollow noreferrer">default</a> is to create a single-node cluster with the name <code>control-plane</code>.  From your description, everything is working properly.</p>
<p>One of kind's core features is the ability to run a &quot;multi-node&quot; cluster, but all locally in containers.  If you want to test your application's behavior if, for example, you drain its pods from a node, you can run a kind cluster with one control-plane node (running etcd, the API server, and other core Kubernetes processes) and three worker nodes; let the application start up, then <code>kubectl drain worker-1</code> and watch what happens.  The documentation also notes that this is useful if you're developing on Kubernetes itself and need a &quot;multi-node&quot; control plan to test HA support.</p>
