Welcome to the Linux Foundation Forum!

Lab 2.1 nodes NotReady state

rfaisal
rfaisal Posts: 2
in LFD259 Class Forum

Hi, I am just starting with the course and was setting up my first lab. I am practicing on AWS and spun the instances up based on the tutorial. I have followed the steps mentioned in lab.2.1 set up. However when I view the nodes, both appear to be in NotReady state.

On running journalctl -u kubelet, I notice and error:
"command failed" err="failed to load kubelet config file, error: failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file \"/var/lib/kubelet/config.yaml\", error: open /var/lib/kubelet/config.yaml: no such file or directory, path: /var/lib/kubelet/config.yaml"

and also,
kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"

I check that the config.yaml file does exist though.

Was wondering if anyone else has faced this issue or know how to move forward with this. Thank you.

Answers

  • chrispokorni
    chrispokorni Posts: 2,606

    Hi @rfaisal,

    What is the guest OS release running the EC2 instances? Are all instances in the same SG and is all inbound traffic allowed from all sources to all port destinations and all protocols?

    Please review the video guide from the introductory chapter for AWS to ensure the infrastructure is correctly configured.

    Regards,
    -Chris

  • rfaisal
    rfaisal Posts: 2

    Hi Chris, thanks for your prompt response. I got this working.

    I had to reboot the ec2 instances. Restarted both control plane and worker plane node, and the state was "Ready" when they came back up.

  • simonblondieau
    simonblondieau Posts: 1

    @rfaisal said:
    Hi Chris, thanks for your prompt response. I got this working.
    I had to reboot the ec2 instances. Restarted both control plane and worker plane node, and the state was "Ready" when they came back up.

    I had the same issue with Azure VMs. Rebooting both worked fine for me as well. Thanks for the tip @rfaisal !

Categories

Upcoming Training