<p>I am following this document to deploy cluster auto scaler in EKS <a href="https://docs.aws.amazon.com/eks/latest/userguide/autoscaling.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/autoscaling.html</a></p>
<p>EKS Version is 1.24. Cluster. Public traffic is allowed on the open internet and we have whitelisted the .amazonaws.com domain in the squid proxy.</p>
<p>I feel there might be something wrong with the role or policy configuration</p>
<p><strong>Error in pod:</strong></p>
<blockquote>
<p>F0208 05:39:52.442470       1 aws_cloud_provider.go:386] Failed to
generate AWS EC2 Instance Types: WebIdentityErr: failed to retrieve
credentials caused by: RequestError: send request failed caused by:
Post &quot;https://sts.us-west-1.amazonaws.com/&quot;: dial tcp
176.32.112.54:443: i/o timeout</p>
</blockquote>
<p>The service account has the annotation in place to make use of the IAM role</p>
<p>Kubectl describes cluster-autoscaler service account</p>
<pre><code>Name:                cluster-autoscaler
Namespace:           kube-system
Labels:              k8s-addon=cluster-autoscaler.addons.k8s.io
                     k8s-app=cluster-autoscaler
Annotations:         eks.amazonaws.com/role-arn: arn:aws:iam::&lt;ID&gt;:role/irsa-clusterautoscaler
Image pull secrets:  &lt;none&gt;
Mountable secrets:   &lt;none&gt;
Tokens:              &lt;none&gt;
Events:              &lt;none&gt;
</code></pre>

Magesh
<p>It was solved by adding the proxy details on the container env of the deployment. Which is missing in the actual documentation, they could add it as a hint. Pod was not taking the proxy setting available in the node, it was expecting it to be configured.</p>
