Alex Leong

We should keep this in sync with the version of cargo deny in the dev container: https://github.com/linkerd/dev/blob/main/Dockerfile#L169C24-L169C31 We can bump this action when the version of cargo deny is similarly...

@halcyondude I think most of the discussion on JWT has been here on this issue. Using `oauth2-proxy` with `nginx-ingress` to provide authenticated access to Linkerd's dashboard seems like a reasonable...

Hi @acald-creator, is there any feedback in particular you're looking for or anything we can do to support you?

Hi @acald-creator Do you think it will be possible to upgrade to v6 without switching the project to React Hooks? Based on my understanding, this would be a significant effort...

hi @efrenaguilar95 I believe what is happening here is that the paths for the observability container's probes are missing the leading slash character. This causes them to fail to be...

@efrenaguilar95 glad to hear it! I've re-titled this issue to "Allow health probe paths without leading slash" and we can use this to track the work of relaxing Linkerd's restrictions...

Hi @ashutosh887, You don't need this issue assigned in order to start work on it. Feel free to just submit a PR or reach out if you have questions.

I'm not sure, but it seems like in this case the path must be absolute and there's simply a bug validating that. i.e. ``` if prefix.starts_with('/') { return Err(InvalidRequestRedirect::RelativePath); }...

@dependabot rebase

Hi @zack-littke-smith! I'd recommend looking at the full client proxy logs, beyond those two log lines in particular. The Linkerd proxy will log when addresses are added to its load...