从专用网络中的EC2到EKS的Kuectl命令正在超时

Question

这个EKS集群只有一个专用端点。我的最终目标是在EKS上部署Helm图表。我通过SSM连接到EC2机器，并且我已经在该机器上安装了Helm和Kuectl。问题是，在专用网络中，无法调用AWS API。因此，我没有调用aws-eks-update-kubeconfig--region region code--name cluster-name，而是创建了如下所示的kubeconfig。

apiVersion: v1
clusters:
- cluster:
server: 1111111111111111.gr7.eu-west-1.eks.amazonaws.com
certificate-authority-data: JTiBDRVJU111111111
name: kubernetes
contexts:
- context:
cluster: kubernetes
user: aws
name: aws
current-context: aws
kind: Config
preferences: {}
users:
- name: aws
user:
exec:
apiVersion: client.authentication.k8s.io/v1alpha1
command: aws
args:
- "eks"
- "get-token"
- "--cluster-name"
- "this-is-my-cluster"
# - "--role-arn"
# - "role-arn"
# env:
# - name: AWS_PROFILE
#   value: "aws-profile"

得到以下错误：

I0127 21:24:26.336266    3849 loader.go:372] Config loaded from file:  /tmp/.kube/config-eks-demo
I0127 21:24:26.337081    3849 round_trippers.go:435] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.21.2 (linux/amd64) kubernetes/d2965f0" 'http://1111111111111111.gr7.eu-west-1.eks.amazonaws.com/api?timeout=32s'
I0127 21:24:56.338147    3849 round_trippers.go:454] GET http://1111111111111111.gr7.eu-west-1.eks.amazonaws.com/api?timeout=32s  in 30001 milliseconds
I0127 21:24:56.338171    3849 round_trippers.go:460] Response Headers:
I0127 21:24:56.338238    3849 cached_discovery.go:121] skipped caching discovery info due to Get "http://1111111111111111.gr7.eu-west-1.eks.amazonaws.com/api?timeout=32s": dial tcp 10.1.1.193:80: i/o timeout

VPC中有连接，NACL、安全组、端口80没有问题。

Answer 1

这看起来像是一个打开的EKS问题：https://github.com/aws/containers-roadmap/issues/298

如果是这样的话，请投赞成票，这样产品团队就可以优先考虑它。如果你有企业支持，你的TAM也可以在这方面提供帮助。