This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

5
Error while initializing a cluster on vmware machines behind a load balancer
Post Body

Hello guys,

I'm receiving this error when i'm trying to initialize a cluster with kubeadm init:

k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://load_balancer_dns:6443/api/v1/services?limit=500&resourceVersion=0: EOF

I'm also receiving other similar errors with v1.Pod and v1.Node, i think it's a connection problem to the load balancer but i can't figure out what exactly.

nc -v LOAD_BALANCER_IP 6443 enstablish a connection which is strange since the official documentation says:

A connection refused error is expected because the apiserver is not yet running. A timeout, however, means the load balancer cannot communicate with the control plane node. If a timeout occurs, reconfigure the load balancer to communicate with the control plane node.

Even if the init fails after i launch the command kubelet is up and running and if i list the containers using docker ps they are all up.

Do you have any idea?

Thanks guys

Author
Account Strength
60%
Account Age
9 years
Verified Email
No
Verified Flair
No
Total Karma
3,092
Link Karma
439
Comment Karma
2,653
Profile updated: 1 day ago
Posts updated: 11 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
4 years ago