CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2kuberneteskubectl
Kuldeep
Kuldeep

Reputation: 659

kubectl get nodes unable to connect to the server on AWS EC2 Instance

I have deployed kubernetes cluster on AWS EC2 Ubuntu Nodes, one master node and one worker node. Its a free tier t2.micro machine with 1 CPU.

I installed and configured everything and on day 1 everything works fine. kubectl get nodes command was responding without any delay and i was able to create MYSQL deployment.

Next day when i tried kubectl get nodes i was getting The connection to the server :6443 was refused - did you specify the right host or port? and even sometimes i am getting Unable to connect to the server: net/http: TLS handshake timeout

I checked the following things to verify whether kubernetes is working or not sudo systemctl status kubelet it was in active status

Even its surprising that sometime kubectl get nodes works perfectly and sometime it return The connection to the server :6443 was refused - did you specify the right host or port?

I am not able to understand how to fix this issue ?

Upvotes: 1

Views: 1598

Answers (1)

davidmontoyago
davidmontoyago

Reputation: 1833

This could be caused by a mismatch between the actual master node IP (apiserver) and the server entry configured in your ~/.kube/config. Verify that they both match and if not, just update the server entry.

Keep in mind that EC2 instances can and will fail (I've seen them randomly crashing even on managed clusters). This could explain why one day your control plane was accessible on one IP and no longer accessible on the next day.

Upvotes: 1

Related Questions