Bug: Cluster terminal doesn't work if hostname label on node doesn't match with node name

[pawan-mehta-dt]

📜 Description

Cluster terminal doesn't work if hostname label on node doesn't match with node name

👟 Reproduction steps

Try creating EKS nodes with DHCP option enabled with your domain
The nodes won't have the hostname label value as node name
Try to create cluster terminal on any of that node

👍 Expected behavior

It should crawl labels on node and use the existing hostname label with value on node

👎 Actual Behavior

Terminal pod creation fails on the node because in affinity devtron adds node name as hostname value

☸ Kubernetes version

EKS 1.23

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[vikramdevtron]

this is fixed in #2925