linkerd failing with timeout

[raid-rohana-healthy]

Hi
Im trying to deploy linkerd in our K8S clusters and it fails with the following error:
linkerd-proxy ● cr.l5d.io/linkerd/proxy:stable-2.11.4 false PostStartHookError: command '/usr/lib/linkerd/linkerd-await --timeout=2m' exited with 69: linkerd-proxy failed to become ready within 120s timeout false 0 on:on 2 4 0:0 0:0 n/a n/a n/a n/a linkerd-proxy:4143,linkerd-admin:4191

Application error log:
failed to start server { ││ error: Error: 14 UNAVAILABLE: No connection established │ at Object.callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:31:26) ││ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:189:52) │ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141) ││ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181) │ at /app/node_modules/@grpc/grpc-js/build/src/call-stream.js:187:78 ││ at processTicksAndRejections (node:internal/process/task_queues:78:11) { │ code: 14, ││ details: 'No connection established', │ metadata: Metadata { internalRepr: Map(0) {}, options: {} } ││ } │ } ││ node:internal/process/promises:265 │ triggerUncaughtException(err, true /* fromPromise */); ││ ^ │ │ Error: 14 UNAVAILABLE: No connection established │ at Object.callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:31:26) │ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:189:52) │ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141) │ at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181) │ at /app/node_modules/@grpc/grpc-js/build/src/call-stream.js:187:78 │ at processTicksAndRejections (node:internal/process/task_queues:78:11) { │ code: 14, │ details: 'No connection established', │ metadata: Metadata { internalRepr: Map(0) {}, options: {} }

Our services is based on nginx and not regular apps. I followed the nginx guide in the doc but without success.
We do however, have a complex network polices applied, could it be the issue? are there any specific ports should be opened for linkerd to work properly ?

[adleong]

Hi @raid-rohana-healthy! I'd recommend looking at the linkerd-proxy container logs to see if there is any information about why it is not becoming ready. This can sometimes be because it cannot get the information it needs from the control plane, but the logs should shed some light on the specific problem.