Alex Leong

Hi @soma-kurisu thanks for all the work you've already done investigating this. We've tried to track down these types of sporadic TLS issues in the past but they've been hard...

Hi @AlexGoris-KasparSolutions. While Linkerd doesn't automatically authorize traffic for grpc probes yet, you should be able to explicitly authorize these probes by creating an AuthorizationPolicy resource for them. We'll look...

Hi @alfaro28! I believe that a targetRef must specify the correct `group`, which should be `gateway.networking.k8s.io` for GRPCRoute.

Thanks for taking this on, @wim-de-groot! Unfortunately, `values.go` is a bit of debt in the codebase. It's been a challenge to keep this typed go struct in sync with the...

Hi @MacroPower. I have to admit I'm not familiar with how inlets work, but I can offer a few observations about your setup. I see that your gateway address is...

That's awesome, thanks for writing up your solution! To be honest, given my lack of familiarity with inlets, it's not clear to me how broadly applicable the solution of using...

I was not able to reproduce this issue. Here are the steps I used: Install linkerd-viz with helm, disabling prometheus and supplying a placeholder prometheusURL: ``` helm install linkerd-viz linkerd/linkerd-viz...

The `--set prometheusUrl=linkerd.io` Helm value will set an annotation on the `linkerd-viz` namespace: ``` kubectl get ns/linkerd-viz -ojsonpath='{.metadata.annotations}' {"viz.linkerd.io/external-prometheus":"linkerd.io"}% ``` It is this annotation which controls if the "prometheus is...

This looks like it might be similar to https://github.com/linkerd/linkerd2-proxy/pull/2928

@dependabot rebase