Alex Leong
Alex Leong
Ah, I think I see what's happening. This value is populated programmatically here: https://github.com/linkerd/linkerd2/blob/main/pkg/charts/linkerd2/values.go#L247 This means that it will be set if Linkerd is installed with the CLI but not...
@AleksandrAksenov Based on the output that you provided, it looks like maybe you have the `linkerd.io/extension=viz` label on the default namespace. This can definitely cause problems because Linkerd uses this...
@Chakki1301 @winterhalder Unless you also have the `linkerd.io/extension=viz` label set on the incorrect namespace, I suspect you may be experiencing a different problem. Please open a new issue with as...
Hi @dwilliams782! If you have at least one `HTTPRoute` defined for a `Server` then any requests to that `Server` which do not match any `HTTPRoute` will result in a 404....
Now that you have removed opaque from those two services, is everything working as desired? I can't say I really understand what's going on here, but if it's working for...
@dwilliams782 Definitely let us know if you can get repro steps for this, we'd love to dig in and understand this better.
I think it would be also good to get rid of where the CLI unnecessarily populates this value here: https://github.com/linkerd/linkerd2/blob/main/pkg/charts/linkerd2/values.go#L247 This makes the behavior more consistent between Helm and the...
Hi @uralsemih. I can confirm that the collector does serve OTLP HTTP on port 4318. However, I have the same questions as @olix0r: I would expect that React should be...
Looking at the collector logs for linkerd stable-2.12.0 I see: ``` 2022-09-15T22:35:14.561Z info otlpreceiver/otlp.go:87 Starting HTTP server on endpoint 0.0.0.0:4318 {"kind": "receiver", "name": "otlp"} ```