Oliver Gould

> I tried to upgrade the trust anchor certtificate and issuer certificate for linkerd. Can you explain in more details what steps you took? > `linkerd-controller-78b96b6f94-sgstq 0/2 CrashLoopBackOff 331 20h`...

@sdhoward This behavior was added because these metrics include high-cardinality labels like ip addresses. For long running proxies--especially in ingresses--these metrics can incur substantial memory overhead. I think we're open...

> There's a race condition I was wrong about this. The webhook should already skip namespaces with the annotation `config.linkerd.io/admission-webhooks: disabled`

> This is becoming a serious problem for us Can you elaborate on the problems you're encountering? What parts of Linkerd don't work with IPv6?

I don't currently have bandwidth to dig into this deeply, but I'll leave some notes here in case someone else has time to investigate: * There's nothing (as far as...

While it's not clear to me whether [k3d supports IPv6 yet](https://github.com/k3d-io/k3d/issues/833), it appears that k3s does. So I suspect it's now possible for us to set up IPv6-only clusters for...

Thanks for trying that, @arianvp. I suspect the `127.0.0.1` is coming from the deployment manifest. You could probably try manually editing it to replace instances of 127.0.0.1 and 0.0.0.0. I'm...

Work for this is in-flight, but I'm uneasy about dropping this in late in the process before the stable release. We should probably figure how to make this an optional...

Linkerd doesn't configure a probe timeout, so you're hitting the kubelet's default timeout of 1s. This should be more than enough time for node-local communication in most environments, but it's...

@snoord I think you're correct. It would be good to add a test that checks that a pod with `automountServiceAccounToken: false` becomes ready