Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Nodes never seem to finish provisioning from the web UI? Question Question
Using floating IP for a one node kubernetes cluster and auto updates Question Question

Question

kubectl: Unable to connect to the server: i/o timeout

Posted May 7, 2020 15k views
KubernetesDigitalOcean Managed Kubernetes

Hi! yesterday I set up a kubernetes cluster on DigitalOcean and today I ran the following steps:

$doctl kubernetes cluster kubeconfig save fyx-cluster
(OK)
$kubectl config current-context
(prints cluster name)
$kubectl apply -f gitlab-admin-service-account.yaml
Unable to connect to the server: dial tcp <IP address>:443: i/o timeout

I run the last command repeatedly, same error.

Now, 10 minutes later, the same command succeeds:

$kubectl apply -f gitlab-admin-service-account.yaml
serviceaccount/gitlab-admin created
clusterrolebinding.rbac.authorization.k8s.io/gitlab-admin created

Is there a way I can avoid these timeouts in the future?

Add a comment
larsblumberg
By:
larsblumberg

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Nodes never seem to finish provisioning from the web UI? Question Question
Using floating IP for a one node kubernetes cluster and auto updates Question Question
Add a comment
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
larsblumberg May 7, 2020

Running the same command a few minutes later, results again in the same error:

$kubectl apply -f gitlab-admin-service-account.yaml
Unable to connect to the server: dial tcp <IP address>:443: i/o timeout

These errors seem to happen sporadically and I’d like to learn how to fix the root cause. My personal internet connection is fine.

Reply Report
Giannis5 January 25, 2021

Hello,
I have the same issue and its happen sporadically. Actually i have 4 kubernetes cluster and I found that the issue are appearing only to one. The only differences is that its the development version and we have a lot of kubernete’s jobs but from the digital ocean reports looks ok. The current status is that is down ( kubernetes access url: https://6474d159-xxxxxxxx-42e8-xxxxxx-6xxxxxxx1cd6e24.k8s.ondigitalocean.com

Unable to connect to the server: dial tcp 165.xxx.xxx.133:443: i/o timeout
Reply Report

Related

Looking for something else?

Ask a new question Search for more help