Welcome to the new Linux Foundation Forum!

Lab 3.1 calico tunnel is not created

hi,
i am on lab 3.1 now,
i follow step by stop of lab 3.1
but after run kubectl apply -f calico.yaml then i check ip a, tunnel is not created and node is not ready also pod is pending

could someone help me please

thanks

Comments

  • chrispokornichrispokorni Posts: 86
    edited October 8

    Hi @nkristianto, could you provide the output from "ip a" and from "kubectl get nodes" and "kubectl get pods -o wide --all-namespaces"?
    Thanks,
    -Chris

  • nkristiantonkristianto Posts: 4
    edited October 8

    hi @chrispokorni this id the output

    i still cannot run the tunnel,
    thanks

  • Thanks for the output. If the master is not ready, it will not allow for any pods to start either.
    Where are you running your nodes? Are you on GCP, AWS, Azure, Virtual box, VMware? What are the sizes of your nodes?
    Were any of the previous outputs inconsistent with the ones presented in the lab (during updates, upgrades, installs)?
    Regards,
    -Chris

  • hi @chrispokorni,
    thanks for your reply

    i am using GCP to running the nodes and i am using n1 standard

    i am following the lab step by step, and nothing different output until step 11

  • There may be such issues when there are not enough resources on the VM for the Kubernetes cluster to start.
    Are they n1-standard-2 with 2 vCPUs and 7.5 GB. Also make sure you have a firewall rule to enable all traffic (all sources, all ports, all protocols).
    New nodes and a re-install have fixed similar issues in the past.
    Regards,
    -Chris

  • hi @chrispokorni
    the issue is fixed

    the root cause is because : yes, you're right. i dont have enough resource to run the nodes

    thanks for the reply
    nkristianto

Sign In or Register to comment.