Welcome to the Linux Foundation Forum!

I am struggling getting past step 11 of lab 3.2

rhopping
rhopping Posts: 6
edited February 20 in LFD259 Class Forum

After I reboot both the cp and worker node in step 10, I am unable to connect to my repo from my cp. I also find kubectl has stopped working. I have a snapshot I can revert to that proves this command was working before step 10.

ryan@k8slab1:~$ curl $repo/v2/_catalog
^C
ryan@k8slab1:~$ echo $repo
10.97.40.62:5000
ryan@k8slab1:~$ kubectl get pods
The connection to the server 172.17.12.202:6443 was refused - did you specify the right host or port?

Answers

  • rhopping
    rhopping Posts: 6
    edited February 20

    I find it actually starts to fail if I reboot after step 4.

    ryan@k8slab1:~$ kubectl version
    Client Version: v1.34.1
    Kustomize Version: v5.7.1
    The connection to the server 172.17.12.202:6443 was refused - did you specify the right host or port?

    ryan@k8slab1:~$ sudo netstat -tulpen
    [sudo] password for ryan:
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
    tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 992 5603 576/systemd-resolve
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 6334 1/init
    tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 992 5605 576/systemd-resolve
    tcp6 0 0 :::22 :::* LISTEN 0 5614 1/init
    udp 0 0 127.0.0.54:53 0.0.0.0:* 992 5604 576/systemd-resolve
    udp 0 0 127.0.0.53:53 0.0.0.0:* 992 5602 576/systemd-resolve
    udp 0 0 172.17.12.202:68 0.0.0.0:* 998 6323 574/systemd-network

  • If I rebuild config.toml, I get kubectl working again. But his of course removes changes your script made.

    sudo containerd config default | sudo tee /etc/containerd/config.toml

  • I am on Ubuntu 24.04.

  • chrispokorni
    chrispokorni Posts: 2,580

    Hi @rhopping,

    Try skipping step 10. There is a chance the config is persisted without reboot.

    Regards,
    -Chris

Categories

Upcoming Training