Cluster information: Kubernetes version:1.28.2 Cloud being used: AWS Installation method: command line Host OS: Ubuntu I have installed Kubernetes on 3 servers, one control plane and two workers. if I issue kubectl get nodes I am receiving error: The connection to the server 172.31.20.146:6443 w…

Hi, Worth checking kubelet and kubeapi logs. ATM no info to work with.

<a name="p-44031-the-issue-youre-encountering-where-the-kubernetes-api-server-at-17231201466443-becomes-inaccessible-shortly-after-a-reboot-suggests-a-problem-that-could-be-related-to-the-kubernetes-control-plane-components-themselves-networking-on-your-host-or-resource-constraints-that-only-manifest-under-certain-conditions-1" class="anchor" href="#p-44031-the-issue-youre-encountering-where-the-kubernetes-api-server-at-17231201466443-becomes-inaccessible-shortly-after-a-reboot-suggests-a-problem-that-could-be-related-to-the-kubernetes-control-plane-components-themselves-networking-on-your-host-or-resource-constraints-that-only-manifest-under-certain-conditions-1" aria-label="Heading link"> The issue you’re encountering, where the Kubernetes API server at 172.31.20.146:6443 becomes inaccessible shortly after a reboot, suggests a problem that could be related to the Kubernetes control plane components themselves, networking on your host, or resource constraints that only manifest under …

Thank you @timwolfe94022 for this CHATGPT generated answer. Maybe I have no great knowledge about Kubernetes, I know how to use chatgpt. @fox-md from journalctl -u kubelet : Feb 16 13:15:17 controlplane kubelet[19063]: E0216 13:15:17.265276 19063 run.go:74] "command failed" err="failed to l> Feb…

Hi, Thank you for logs. Seems that kubelet keeps crashing. Check syslogs.

Hey @fox-md , Here is the output from syslog, looks like there is an issue with the Calico network, but I am not too sure if I am getting this correct. Feb 18 08:59:48 controlplane kubelet[838]: E0218 08:59:48.050058 838 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"Start…

Hi, Calico cannot connect to kubeapi server. There must be a reason of the kubelet failure. You need to have it in the running state, otherwise static pods will not start. Can you check /var/log/syslog file? There should be some info related to kubelet.

AWS Unable to connect to the Kubernetes API server on port 6443

General Discussions

Angry_Admin February 20, 2024, 5:32pm 8

Thank you @fox-md , it was Calico, I rebuilt the cluster with new custom resources from Calico and everything works as a charm.

https://raw.githubusercontent.com/projectcalico/calico/v3.26.1/manifests/custom-resources.yaml

Topic		Replies	Views
The connection to the server 192.168.1.2:6443 was refused - did you specify the right host or port? General Discussions	9	46613	May 2, 2025
The connection to the server <host>:6443 was refused - did you specify the right host or port? General Discussions	81	589027	January 7, 2025
The connection to the server Master_IP:6443 was refused - did you specify the right host or port? General Discussions development , security , network , kubernetes-custom-resources	0	1625	June 3, 2024
Migrated VMs that has Kubernetes from AWS to Azure, but kube-apiserver pod is getting failed General Discussions docs , development , podcast , network	2	96	January 24, 2025
Kube-apiserver is gone / The connection to the server master:6443 was refused - did you specify the right host or port? General Discussions	4	3861	February 1, 2024

AWS Unable to connect to the Kubernetes API server on port 6443

Related topics