linkerd2 proxy-injector readiness probe fails with 502

[arikt-ms]

Hi, I am getting the following error on installing linkerd2 v2.11.x

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: "linkerd-heartbeat" namespace: "linkerd" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first

I found this github issue explaining that the linkerd-heartbeat api version needs to be changed to v1 and tried that. Now, the installation starts, however the linked check reports an error with proxy-injector pod.

`Linkerd core checks

===================

kubernetes-api

---

√ can initialize the client

√ can query the Kubernetes API

kubernetes-version

---

√ is running the minimum Kubernetes API version

√ is running the minimum kubectl version

linkerd-existence

---

√ 'linkerd-config' config map exists

√ heartbeat ServiceAccount exist

√ control plane replica sets are ready

√ no unschedulable pods

× control plane pods are ready

pod/linkerd-proxy-injector-76d5f6c57d-v8c42 container proxy-injector is not ready

see https://linkerd.io/2.12/checks/#l5d-api-control-ready for hints

Status check results are ×`

Upon closer inspection of the pod I see that the proxy-injector container in the pod fails the readiness probe:

`Events:

Type Reason Age From Message

---

Normal Scheduled 6m13s default-scheduler Successfully assigned linkerd/linkerd-proxy-injector-76d5f6c57d-v8c42 to aks-agentpool-92195387-vmss000001

Normal Pulling 6m13s kubelet Pulling image "cr.l5d.io/linkerd/proxy-init:v1.5.3"

Normal Pulled 6m5s kubelet Successfully pulled image "cr.l5d.io/linkerd/proxy-init:v1.5.3" in 7.873430423s

Normal Created 6m5s kubelet Created container linkerd-init

Normal Started 6m5s kubelet Started container linkerd-init

Normal Pulling 6m4s kubelet Pulling image "cr.l5d.io/linkerd/proxy:stable-2.11.5"

Normal Pulled 5m52s kubelet Successfully pulled image "cr.l5d.io/linkerd/proxy:stable-2.11.5" in 11.446888746s

Normal Created 5m52s kubelet Created container linkerd-proxy

Normal Started 5m52s kubelet Started container linkerd-proxy

Normal Created 5m47s kubelet Created container proxy-injector

Normal Started 5m47s kubelet Started container proxy-injector

Warning Unhealthy 5m13s (x3 over 5m33s) kubelet Liveness probe failed: HTTP probe failed with statuscode: 502

Normal Killing 5m13s kubelet Container proxy-injector failed liveness probe, will be restarted

Normal Pulled 4m47s (x2 over 5m47s) kubelet Container image "cr.l5d.io/linkerd/controller:stable-2.11.5" already present on machine

Warning Unhealthy 63s (x47 over 5m47s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 502`

Any idea how to workaround this ?