CODEWITHSUNDEEP
kubernetescoreoscoreos-ignition
dippynark
dippynark

Reputation: 3003

Bootkube API server unable to start

I am following the CoreOS tutorial for self-hosted Kubernetes and I am having some issues with the Bootkube API server. Using the Bootkube example from the recommended repository I have only changed the ssh_authorized_keys metadata field in nodes 1,2 and 3. All other settings are the same as in the repository. However, after running bootkube-start via systemctl on node1 I check the logs using ssh [email protected] 'journalctl -f -u bootkube' and I am getting Unable to determine api-server readiness: Get https://node1.example.com:443/version: dial tcp 172.17.0.21:443: getsockopt: connection refused. Does anyone know of the best ways to debug such an issue?

Upvotes: 1

Views: 564

Answers (1)

kaeso
kaeso

Reputation: 341

It looks like the api-server is having issues while starting, or that you have some networking/firewall/dns problem.

You should be able to ssh [email protected] and then get the full bootkube logs there via sudo journalctl -u bootkube.

Upvotes: 0

Related Questions