From 623347b4d9cf55f032c97a2eef39d932e50645ca Mon Sep 17 00:00:00 2001 From: Satvik Mishra Date: Fri, 9 Oct 2026 15:32:13 +0530 Subject: [PATCH] docs: fix broken section anchors in 2-edge and 2.19 docs Several in-page links point at heading anchors that no longer exist (sections were renamed or a typo crept in), so the browser lands at the top of the page instead of the referenced section: - circuit-breaking: #meshed-conncections typo, and the proxy-metrics link now points at #endpoint-metrics, where outbound_http_balancer_endpoints is documented - authorization-policy, fault-injection, configuring-per-route-policy: httproute #linkerd-and-gateway-api-httproutes -> #the-policylinkerdio-group - multicluster: automatic-mtls #how-does-it-work -> #how-does-linkerds-mtls-implementation-work - troubleshooting: server-policy #policy-annotations -> #default-policies - upgrade: install-helm #helm-upgrade-procedure -> #upgrading-with-helm Signed-off-by: Satvik Mishra --- linkerd.io/content/2-edge/reference/authorization-policy.md | 2 +- linkerd.io/content/2-edge/reference/circuit-breaking.md | 4 ++-- .../content/2-edge/tasks/configuring-per-route-policy.md | 2 +- linkerd.io/content/2-edge/tasks/fault-injection.md | 2 +- linkerd.io/content/2-edge/tasks/multicluster.md | 2 +- linkerd.io/content/2-edge/tasks/troubleshooting.md | 2 +- linkerd.io/content/2-edge/tasks/upgrade.md | 2 +- linkerd.io/content/2.19/reference/authorization-policy.md | 2 +- linkerd.io/content/2.19/reference/circuit-breaking.md | 4 ++-- linkerd.io/content/2.19/tasks/configuring-per-route-policy.md | 2 +- linkerd.io/content/2.19/tasks/fault-injection.md | 2 +- linkerd.io/content/2.19/tasks/multicluster.md | 2 +- linkerd.io/content/2.19/tasks/troubleshooting.md | 2 +- linkerd.io/content/2.19/tasks/upgrade.md | 2 +- 14 files changed, 16 insertions(+), 16 deletions(-) diff --git a/linkerd.io/content/2-edge/reference/authorization-policy.md b/linkerd.io/content/2-edge/reference/authorization-policy.md index ed9eebd254..30b4610cd7 100644 --- a/linkerd.io/content/2-edge/reference/authorization-policy.md +++ b/linkerd.io/content/2-edge/reference/authorization-policy.md @@ -187,7 +187,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2-edge/reference/circuit-breaking.md b/linkerd.io/content/2-edge/reference/circuit-breaking.md index c3f551254b..bb8b0d3c7c 100644 --- a/linkerd.io/content/2-edge/reference/circuit-breaking.md +++ b/linkerd.io/content/2-edge/reference/circuit-breaking.md @@ -206,9 +206,9 @@ configure parameters for the unified failure accrual policy: [circuit-breaker]: https://www.martinfowler.com/bliki/CircuitBreaker.html [503 Service Unavailable]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503 -[metric]: proxy-metrics/#outbound-xroute-metrics +[metric]: proxy-metrics/#endpoint-metrics [5xx server error]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses [exp-backoff]: https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/ -[outbound]: architecture/#meshed-conncections +[outbound]: architecture/#meshed-connections diff --git a/linkerd.io/content/2-edge/tasks/configuring-per-route-policy.md b/linkerd.io/content/2-edge/tasks/configuring-per-route-policy.md index 16dbc96142..1a9fcb4ed9 100644 --- a/linkerd.io/content/2-edge/tasks/configuring-per-route-policy.md +++ b/linkerd.io/content/2-edge/tasks/configuring-per-route-policy.md @@ -196,7 +196,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2-edge/tasks/fault-injection.md b/linkerd.io/content/2-edge/tasks/fault-injection.md index 5172a374a0..38363f20ea 100644 --- a/linkerd.io/content/2-edge/tasks/fault-injection.md +++ b/linkerd.io/content/2-edge/tasks/fault-injection.md @@ -181,7 +181,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2-edge/tasks/multicluster.md b/linkerd.io/content/2-edge/tasks/multicluster.md index e0c8c81185..45782ced53 100644 --- a/linkerd.io/content/2-edge/tasks/multicluster.md +++ b/linkerd.io/content/2-edge/tasks/multicluster.md @@ -78,7 +78,7 @@ certificates that it receives from peers as part of the mTLS handshake. With a common base of trust, we now need to generate a certificate that can be used in each cluster to issue certificates to the proxies. If you'd like to get a deeper picture into how this all works, check out the -[deep dive](../features/automatic-mtls/#how-does-it-work). +[deep dive](../features/automatic-mtls/#how-does-linkerds-mtls-implementation-work). The trust anchor that we've generated is a self-signed certificate which can be used to create new certificates (a certificate authority). To generate the diff --git a/linkerd.io/content/2-edge/tasks/troubleshooting.md b/linkerd.io/content/2-edge/tasks/troubleshooting.md index 929d16c5fe..1adb3d046f 100644 --- a/linkerd.io/content/2-edge/tasks/troubleshooting.md +++ b/linkerd.io/content/2-edge/tasks/troubleshooting.md @@ -2027,7 +2027,7 @@ Example failure: ``` This warning indicates that the listed pods have the -[`deny` default inbound policy](../features/server-policy/#policy-annotations), +[`deny` default inbound policy](../features/server-policy/#default-policies), which may prevent the `linkerd-viz` Prometheus instance from scraping the data plane proxies in those pods. If Prometheus cannot scrape a data plane pod, `linkerd viz` commands targeting that pod will return no data. diff --git a/linkerd.io/content/2-edge/tasks/upgrade.md b/linkerd.io/content/2-edge/tasks/upgrade.md index de7bb0d704..4a843523f9 100644 --- a/linkerd.io/content/2-edge/tasks/upgrade.md +++ b/linkerd.io/content/2-edge/tasks/upgrade.md @@ -110,7 +110,7 @@ linkerd prune | kubectl delete -f - ### Upgrading the control plane with Helm For Helm control plane installations, please follow the instructions at -[Helm upgrade procedure](install-helm/#helm-upgrade-procedure). +[Helm upgrade procedure](install-helm/#upgrading-with-helm). ### Verifying the control plane upgrade diff --git a/linkerd.io/content/2.19/reference/authorization-policy.md b/linkerd.io/content/2.19/reference/authorization-policy.md index ed9eebd254..30b4610cd7 100644 --- a/linkerd.io/content/2.19/reference/authorization-policy.md +++ b/linkerd.io/content/2.19/reference/authorization-policy.md @@ -187,7 +187,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2.19/reference/circuit-breaking.md b/linkerd.io/content/2.19/reference/circuit-breaking.md index 3c56a1c1fd..21b8dfc2aa 100644 --- a/linkerd.io/content/2.19/reference/circuit-breaking.md +++ b/linkerd.io/content/2.19/reference/circuit-breaking.md @@ -157,9 +157,9 @@ configure parameters for the consecutive-failures failure accrual policy: [circuit-breaker]: https://www.martinfowler.com/bliki/CircuitBreaker.html [503 Service Unavailable]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503 -[metric]: proxy-metrics/#outbound-xroute-metrics +[metric]: proxy-metrics/#endpoint-metrics [5xx server error]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses [exp-backoff]: https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/ -[outbound]: architecture/#meshed-conncections +[outbound]: architecture/#meshed-connections diff --git a/linkerd.io/content/2.19/tasks/configuring-per-route-policy.md b/linkerd.io/content/2.19/tasks/configuring-per-route-policy.md index 88d6176938..9c19dfdb81 100644 --- a/linkerd.io/content/2.19/tasks/configuring-per-route-policy.md +++ b/linkerd.io/content/2.19/tasks/configuring-per-route-policy.md @@ -196,7 +196,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2.19/tasks/fault-injection.md b/linkerd.io/content/2.19/tasks/fault-injection.md index 5172a374a0..38363f20ea 100644 --- a/linkerd.io/content/2.19/tasks/fault-injection.md +++ b/linkerd.io/content/2.19/tasks/fault-injection.md @@ -181,7 +181,7 @@ Two versions of the HTTPRoute resource may be used with Linkerd: The two HTTPRoute resource definitions are similar, but the Linkerd version implements experimental features not yet available with the upstream Gateway API resource definition. See -[the HTTPRoute reference documentation](../reference/httproute/#linkerd-and-gateway-api-httproutes) +[the HTTPRoute reference documentation](../reference/httproute/#the-policylinkerdio-group) for details. {{< /note >}} diff --git a/linkerd.io/content/2.19/tasks/multicluster.md b/linkerd.io/content/2.19/tasks/multicluster.md index e0c8c81185..45782ced53 100644 --- a/linkerd.io/content/2.19/tasks/multicluster.md +++ b/linkerd.io/content/2.19/tasks/multicluster.md @@ -78,7 +78,7 @@ certificates that it receives from peers as part of the mTLS handshake. With a common base of trust, we now need to generate a certificate that can be used in each cluster to issue certificates to the proxies. If you'd like to get a deeper picture into how this all works, check out the -[deep dive](../features/automatic-mtls/#how-does-it-work). +[deep dive](../features/automatic-mtls/#how-does-linkerds-mtls-implementation-work). The trust anchor that we've generated is a self-signed certificate which can be used to create new certificates (a certificate authority). To generate the diff --git a/linkerd.io/content/2.19/tasks/troubleshooting.md b/linkerd.io/content/2.19/tasks/troubleshooting.md index 603db116aa..ffcfb40354 100644 --- a/linkerd.io/content/2.19/tasks/troubleshooting.md +++ b/linkerd.io/content/2.19/tasks/troubleshooting.md @@ -1854,7 +1854,7 @@ Example failure: ``` This warning indicates that the listed pods have the -[`deny` default inbound policy](../features/server-policy/#policy-annotations), +[`deny` default inbound policy](../features/server-policy/#default-policies), which may prevent the `linkerd-viz` Prometheus instance from scraping the data plane proxies in those pods. If Prometheus cannot scrape a data plane pod, `linkerd viz` commands targeting that pod will return no data. diff --git a/linkerd.io/content/2.19/tasks/upgrade.md b/linkerd.io/content/2.19/tasks/upgrade.md index de7bb0d704..4a843523f9 100644 --- a/linkerd.io/content/2.19/tasks/upgrade.md +++ b/linkerd.io/content/2.19/tasks/upgrade.md @@ -110,7 +110,7 @@ linkerd prune | kubectl delete -f - ### Upgrading the control plane with Helm For Helm control plane installations, please follow the instructions at -[Helm upgrade procedure](install-helm/#helm-upgrade-procedure). +[Helm upgrade procedure](install-helm/#upgrading-with-helm). ### Verifying the control plane upgrade