Error getting server version: Get "https://10.96.0.1:443/version?timeout=32s"

[ilmal]

Heyo,

I've been using this for a while now without any problems, but all of a sudden my pod kept on crashing and spitting out the err message:

F1121 17:35:15.868874 1 provisioner.go:247] Error getting server version: Get "https://10.96.0.1:443/version?timeout=32s": dial tcp 10.96.0.1:443: i/o timeout

What should I do to fix this?

Thanks

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ilmal]

The problem seemed to be from my networking pods not configured correctly. And so not from nfs.

[angelosnm]

@ilmal How exactly did you resolve the pods networking issues?

[yonatankahana]

@ilmal How exactly did you resolve the pods networking issues?

if you don't have pod networking (e.g calico, flannel) installed then you should install one.

if you have pod networking installed and it's not working, you should troubleshoot the problem depends on what you have installed. for example if you use calico you can read its pods logs (calico-node-*).

read more: https://kubernetes.io/docs/concepts/cluster-administration/networking/

[angelosnm]

@ilmal How exactly did you resolve the pods networking issues?

if you don't have pod networking (e.g calico, flannel) installed then you should install one.

if you have pod networking installed and it's not working, you should troubleshoot the problem depends on what you have installed. for example if you use calico you can read its pods logs (calico-node-*).

read more: https://kubernetes.io/docs/concepts/cluster-administration/networking/

@yonatankahana I'm using weave net as my pod networking solution. You think that this may be the issue? I will test with calico & flannel as well. Thanks anyway! 🥇

[ilmal]

Hi!
Sorry for late reply.

The problem I had was with flannel networking and not with nfs at all. I later found out that none of my pods had internet access. And so, that is why I got this error.

It was a while ago, but if I remember correctly the problem I had was with taints and tolerations. I was messing around with these and put taints on a majority of the nodes. That lead to my networking pods not starting up on all the nodes, which resulted in my pods not having access to the internet. (The networking applications need to run a pod on every single node in order to work properly)

So, my solution was to simply allow my networking pods to run on every node.

Although, I will mention. While troubleshooting this problem I found that most people that have problems with networking has trouble with DNS.

I would advise you to start debugging here: https://vexxhost.com/blog/its-always-dns/

[angelosnm]

Hi!

No worries for the reply!

@yonatankahana comment "unblocked" me as I figured that the issue was related with the weave net. I installed calico in my cluster, and everything is working smoothly up until now!

Thank you both guys for your help!