Welcome to the Linux Foundation Forum!

Lab 3.2 Cant access cluster after Reboot

Options

I have setup my cluster in GCE like shown in the video of the course. Everything works fine. Then i setup the local repo in Lab 3.2 and i restarted like written in the manual. After restart i get following error when i want to access my cluster:

student@worker:~$ kubectl cluster-info
E0301 11:03:52.843058 5871 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0301 11:03:52.843469 5871 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0301 11:03:52.844927 5871 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0301 11:03:52.846334 5871 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0301 11:03:52.847657 5871 memcache.go:238] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server localhost:8080 was refused - did you specify the right host or port?

I setup the VM for the second time and i get the same error again afte reboot, what am i making wrong?

thanks.

Comments

  • chrispokorni
    chrispokorni Posts: 2,208
    Options

    Hi @jola1987,

    The errors you see are expected when attempting to run kubectl commands on the worker node.
    The kubectl command is only configured to run from the control plane node, if the installation and configuration steps were closely followed.

    Regards,
    -Chris

Categories

Upcoming Training