This message was deleted.
# ask-communitys
Slackbot
03/01/2023, 3:33 PMThis message was deleted.
c
Christopher Boyd
03/01/2023, 3:53 PM Copy code
Kubernetes cluster unreachable:
Get "<https://138D694E8B25E092453A8779998D4CCB.gr7.us-east-1.eks.amazonaws.com/version>":
dial tcp 10.212.10.232:443: i/o timeoutChristopher Boyd
03/01/2023, 3:53 PMseems like a connection issue?
m
MT
03/01/2023, 4:00 PMYes, but I am not sure about the solution. Cluster is created but does not communicate.
c
Christopher Boyd
03/01/2023, 4:28 PMdo you have kubectl installed? with a profile specifed, can you run kubectl get nodes? or
aws eks list-clustersm
MT
03/01/2023, 4:54 PM Copy code
$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.24.7-eks-fb459a0
Kustomize Version: v4.5.4
The connection to the server localhost:8080 was refused - did you specify the right host or portMT
03/01/2023, 4:55 PMand
aws eks list-clustersc
Christopher Boyd
03/01/2023, 8:37 PMIt doesn’t look like you are connected to any cluster via kubectl
Christopher Boyd
03/01/2023, 8:38 PMdo you have a kubeconfig ? You can check
echo $KUBECONFIGls -l ~/.kube/Christopher Boyd
03/01/2023, 8:38 PMI’d check to see that you can actually connect, from what I can see here, it looks like maybe the cluster is there, but you have firewall / connection issues with the helm prefect deployment piece
m
MT
03/03/2023, 6:12 PMThank you Christopher. There is no kubeconfig file and no /.kube directory even though I followed steps here .