fix legacy link

hashicorp · Feb 23, 2023 · 9a17957 · 9a17957
1 parent 6863c6e
commit 9a17957
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/website/content/docs/k8s/connect/cluster-peering/usage/l7-traffic.mdx b/website/content/docs/k8s/connect/cluster-peering/usage/l7-traffic.mdx
@@ -25,7 +25,7 @@ To configure L7 traffic management behavior in deployments with cluster peering
 
 1. Define the peer cluster as a failover target in the service resolver configuration. 
 
-  The following example updates the [`service-resolver` CRD](/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.
+  The following example updates the [`service-resolver` CRD](/consul/docs/connect/config-entries/) in `cluster-01` so that Consul redirects traffic intended for the `frontend` service to a backup instance in peer `cluster-02` when it detects multiple connection failures.
 
   ```yaml
   apiVersion: consul.hashicorp.com/v1alpha1