<p>Both Logs/ Exec commands are throwing tls error:</p>
<pre><code>$ kubectl logs &lt;POD-NAME&gt;

Error from server: Get &quot;https://&lt;NODE-PRIVATE-IP&gt;:10250/containerLogs/&lt;NAMESPACE&gt;/&lt;POD-NAME&gt;/&lt;DEPLOYMENT-NAME&gt;&quot;: remote error: tls: internal error

</code></pre>
<pre><code>$ kubectl exec -it &lt;POD-NAME&gt; -- sh

Error from server: error dialing backend: remote error: tls: internal error
</code></pre>

<p>Check if your hostname type setting in the subnet and launch template configuration is using resource name and if that is the case then switch to using IP name instead. I think this is caused by some weird pattern matching going on with the AWS EKS control plane (as of v1.22) where it would not issue a certificate for a node if that node's hostname doesn't match its requirements. You can test this quickly by adding another node group to your cluster with the nodes' hostnames set to IP name.</p>
