Describe the bug
When attempting to open a shell at the node level, the "node-shell" pod gets stuck in pending and never starts.

To Reproduce
Steps to reproduce the behavior:

1. Go to Nodes, select a Node and open "Shell"
2. Terminal window opens below with "Connecting ..." and never moved ahead from that.
3. From the Pods view, it shows a "node-shell" pod in Pending status, but never changes or starts.

Expected behavior
I expect to get a terminal window running on the Node.

Environment (please complete the following information):

• Lens Version: 3.6.7
• OS: Windows 10
• K8s environment: AWS EKS

Additional context
I expect it to be a mismatch in the pod's node affinity.
My node has the following properties:

• Name: "ip-10-86-40-168.us-west-2.compute.internal".
• Label: kubernetes.io/hostname=ip-10-86-40-168.mydomain.com

However, Lens creates the pod with the following nodeSelector:

  nodeSelector:
    kubernetes.io/hostname: ip-10-86-40-168.us-west-2.compute.internal

It seems to be using the Name of the node in the selector, yet matching against the label kubernetes.io/hostname which doesn't always match the Name of the Node, which in my case, it does not match, causing the pod to never start because the matching node doesn't exist.