Alejandro Pedraza

@grampelberg Nope, that still hasn't landed #4235

The pod's in linkerd's control plane require that token in order to connect to the kube-api, as do the proxies in the data plane in order to bootstrap their identity....

I'm afraid I can't give you a lot of guidance here without having a reproducible scenario. We have some docs about [failfast](https://linkerd.io/2.15/common-errors/failfast/) and [503 and 504 errors](https://linkerd.io/2.15/common-errors/http-503-504/) that might help....

Can you share what linkerd version you're on? There was an issue with readiness probes taking a long time to succeed, but that was fixed some time ago.

Hi @kristjankullerkann-wearemp, I think it would be valuable to add configurability to the probes. Are you up to push a PR with this? I'd be glad to provide some guidance....

The issue stems from us [passing logrus' standard logger to klog](https://github.com/linkerd/linkerd2/blob/edge-24.7.4/pkg/flags/flags.go#L47), which uses an [InfoLevel by default](https://github.com/sirupsen/logrus/blob/v1.9.3/logger.go#L92). We could easily change that level to Debug, and have all client-go log...

Thanks again for the help @Aransh ! Here's the info you need: - In the `linkerd-viz` and `linkerd-jaeger` charts, all workloads require kube-api access - In multicluster's `linkerd-multicluster` chart, the...

Yeah these are all single-container pods (not counting the proxy and init containers, which don't require any changes).

Turns out those docs are outdated... the right command is `go test ./... -update`

Addressed in #14206; will be available in edge-25.7.3