Welcome to the Linux Foundation Forum!

Issues setting up Linkerd

I have been trying to install the service mesh linkered for the course exercise but it keeps failing. When I describe the pods I see a readiness prob error. There is not a lot of help for how to fix this on the linkerd site

Normal Pulled 86s (x2 over 3m58s) kubelet Container image "cr.l5d.io/linkerd/proxy:stable-2.12.0" already present on machine
Warning Unhealthy 86s kubelet Readiness probe failed: Get "http://192.168.54.68:9996/ready": dial tcp 192.168.54.68:9996: connect: connection refused
Warning Unhealthy 86s kubelet Readiness probe failed: Get "http://192.168.54.68:9997/ready": dial tcp 192.168.54.68:9997: connect: connection refused
Warning Unhealthy 78s kubelet Readiness probe failed: Get "http://192.168.54.68:9996/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 78s kubelet Liveness probe failed: Get "http://192.168.54.68:9990/live": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 78s kubelet Readiness probe failed: Get "http://192.168.54.68:9997/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Answers

  • chrispokorni
    chrispokorni Posts: 1,552

    Hi @itsmarydan,

    With the recent release of Linkerd 2.12, critical changes in the install and config are causing these issues. However, if downgrading to Linkerd 2.11, you should be able to complete the lab as presented.

    To install Linkerd 2.11:

    export LINKERD2_VERSION=stable-2.11.4

    curl -sL run.linkerd.io/install | sh

    ... and continue with the installation steps from the lab guide.

    Then eventually in Lab 11.2 step 11 you may need to modify the command to the following:

    kubectl get ds myingress-ingress-nginx-controller -o yaml | linkerd inject --ingress --skip-inbound-ports 443 --skip-outbound-ports 443 - | kubectl apply -f -

    Regards,
    -Chris

Categories

Upcoming Training