Ayushi Srivastava

Hi @olix0r, I tried the repro described and the pod stays in ContainerCreating stage. I haven't looked into the logs as ephemeral containers aren't enabled on our clusters right now,...

Well, even in the container creating stage, the curl commands works just fine ``` 100 165 100 165 0 0 7168 0 --:--:-- --:--:-- --:--:-- 7500 2022-05-17T19:21:09.19905971Z stderr F %...

Also to put it out, linkerd-proxy-injector and linkerd-destination stay in a CrashLoopBackOff with the following error initially: ``` PostStartHookError: rpc error: code = Unknown desc = failed to exec in...

@adleong thanks for pointing that out! Fixing that got my linkerd-identity pods up and running, but the destination and proxy-injector are still failing with: `linkerd-proxy [ 118.692279s] WARN ThreadId(02) identity:controller{addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}:endpoint{addr=10.244.3.137:8080}:...

@adleong @olix0r any suggestions here? We're stuck on an upgrade

Hey, we recently added the changes in our linkerd's values file to pickup controller images for Microsoft's internal container registry, which I missed updating while updating the helm chart version....

I found [this](https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/) doc on DNS issue debugs. ``` kubectl exec -i -t dnsutils -- nslookup linkerd-identity-headless.linkerd.svc.cluster.local ─╯ Server: 10.0.0.10 Address: 10.0.0.10#53 ** server can't find linkerd-identity-headless.linkerd.svc.cluster.local: NXDOMAIN command terminated...

> @ayushiaks are you in the Linkerd slack? It would be great to connect a little more synchronously to see what we can do. Not yet, thanks will join it!...

@olix0r @adleong any updates here? 2.11.0 also started failing for us now :|

Hi @olix0r , We're at linkerd 2.11.0 now, which is working fine. There were some transient issues with it. (2.11.1 and 2.11.2 are still causing above issues^) To repro this,...