Geek Answers Handbook

Kubernetes Unable to Connect to New CoreOS Installation

I am running (from Windows 8.1) Vagrant VM for CoreOS ( yungsang / coreos ).

I installed kubernetes according to the manual I found here and created json for pod using my images.

When I execute sudo ./kubecfg list /pods, I get the following error:

F0909 06:03:04.626251 01933 kubecfg.go:182] Got request error: Get http://localhost:8080/api/v1beta1/pods?labels=: dial tcp 127.0.0.1:8080: connection refused

Same for sudo ./kubecfg -h http://127.0.0.1:8080 -c /vagrant/app.json create /pods

EDIT: Update

Instead of running the commands myself, I integrated into a stray file ( such as this ).

This makes kubernetes workable. HOWEVER, after some time, my wandering ssh connection closes. I reconnect, and any kubernetes commands I indicate the result with the same error as above.

EDIT 2: Update

I managed to run it again, however I'm not sure if it will work smoothly

I had to re-execute the following commands.

sudo systemctl start etcd
sudo systemctl start download-kubernetes
sudo systemctl start apiserver
sudo systemctl start controller-manager
sudo systemctl start kubelet
sudo systemctl start proxy

I believe apirusver actually needs a restart

What is the source of this timeout? (Where are any magazines I can find on this)

+4
source share
3 answers

Kubernetes , . , . , , , .

, , , Kubecfg kubectl. , , - :

./kubectl get pods.

kubectl env, kubectl , apirusver:

KUBERNETES_MASTER=http://IPADDRESS:8080.

, , CoreOS, - . , kube-apiserver, , , :

journalctl -f -u kube-apiserver

node, apirusver. , , :

systemctl start kube-apiserver

+3

CoreOS , journalctl.

, etcd, , journalctl _COMM=etcd, journalctl _COMM=apiserver apiserver, .

, systemctl status apiserver.

0

errordevelopers, .

systemctl status apiserver sudo systemctl start apiserver .

0

More articles:


All Articles