Kevin Leimkuhler

I'm not sure I understand the situation where the `proxy-init` container is running but finding existing proxy rules. #5786 could explain it, but do you think that is likely on...

> These pods will get restarted periodically, so most likely what happens is that a client pod (with `linkerd-init` container) lands on a node that previously had a `linkerd-init` set...

Yea it seems like we could add `GODEBUG=netdns=cgo` to the `darwin-full` and `darwin-arm64-full` build stages in the CLI's [Dockerfile](https://github.com/linkerd/linkerd2/blob/5491aec246a60552ee72fe73071cdf00b5bdc7ee/cli/Dockerfile).

@jcogilvie Changing this to be more configurable sounds like a good plan. I would probably keep `controlPlaneTracing` as a boolean, and change `controlPlaneTracingNamespace` to something like ```yaml controlPlaneTracingCollector: name: collector...

Thanks for the thoughts on this @ripta. I'd like to preface that ServerAuthorizations haven't been deprecated, but the more flexible resource — AuthorizationPolicies — were introduced in 2.12 as explained...

There are 2 places we check that the CRDs exist in 2.12's CLI: `linkerd check --crds` and `linkerd check`. If either of these are being run on a 2.11 or...

#9287 was closed as this felt like a grody fix to the larger issue that `linkerd check` is version agnostic. If we are to fix this issue, it should be...

Similar to what we do with the Rust side of things, we may want to consider downgrading `client-go` to the minimum supported k8s version instead.

@dependabot rebase

I don't think this is an issue; you should be able to fix this if you change `linkerd multicluster install`. The gateway identity used in cross-cluster communication is retrieved from...