linkerd

We're on 5.3.0 and would like to upgrade to v6, but that's a breaking change that requires manual intervention in our routes handling.

The React-router project has promised a compatibility layer to come up at some point that would avoid having to change things too much, but I feel that's a second-best solution and would prefer to have things written as per the best practice.

For anyone w

Describe the bug

The documentation and some tests uses gw.ns(.svc.cluster.local) for gateways.

I think this is the correct format for istio gateways: <gateway namespace>/<gateway name>

Like here:

https://github.com/fluxcd/flagger/blob/273b05fb24d467c10939389218e6a8ec26d4c70e/test/istio/test-delegation.sh#L41

re. https://istio.io/latest/docs/reference/config/networking/virtua

Current State

Clicking the contributing breadcrumb (See top of first image) leads to a 404

On link in

Current Behavior
The Pingdom Website Speed Test of layer5.io currently receives a low score. Suggestions are made in the test as to how to speed up the layer5.io site.

Desired Situation
Implement the suggestions and improve the site speed and speed score.

Contributor Resources

The layer5.io website uses Gatsby, React, and G

Authorization Policy. Linkerd can restrict which types of traffic are allowed to .
-->
Authorization Policy. Linkerd can restrict which types of traffic are allowed to.

WebSite Link - https://linkerd.io/2.11/features