From bc6859640d7b0dbfb7f1a641c64ddc6060d6c9c1 Mon Sep 17 00:00:00 2001 From: Satvik Mishra Date: Fri, 9 Oct 2026 18:59:37 +0530 Subject: [PATCH] docs: fix stale dashboard, Grafana and books links The viz dashboard and Grafana are no longer described on the architecture page, so point these links at features/dashboard (#linkerd-dashboard and #grafana) instead. The books demo no longer has a service-profiles section, so link to the demo page itself. Applied to 2-edge and 2.19. Signed-off-by: Satvik Mishra --- linkerd.io/content/2-edge/reference/cli/viz.md | 2 +- linkerd.io/content/2-edge/tasks/exposing-dashboard.md | 2 +- linkerd.io/content/2-edge/tasks/setting-up-service-profiles.md | 2 +- linkerd.io/content/2.19/reference/cli/viz.md | 2 +- linkerd.io/content/2.19/tasks/exposing-dashboard.md | 2 +- linkerd.io/content/2.19/tasks/setting-up-service-profiles.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/linkerd.io/content/2-edge/reference/cli/viz.md b/linkerd.io/content/2-edge/reference/cli/viz.md index da24ef2e19..e60d25f89b 100644 --- a/linkerd.io/content/2-edge/reference/cli/viz.md +++ b/linkerd.io/content/2-edge/reference/cli/viz.md @@ -40,7 +40,7 @@ title: viz {{< cli-description "viz dashboard" >}} -Check out the [architecture](../architecture/#dashboard) docs for a more +Check out the [dashboard](../../features/dashboard/#linkerd-dashboard) docs for a more thorough explanation of what this command does. {{< cli-examples "viz dashboard" >}} diff --git a/linkerd.io/content/2-edge/tasks/exposing-dashboard.md b/linkerd.io/content/2-edge/tasks/exposing-dashboard.md index 0f0d9ef682..3baa123db6 100644 --- a/linkerd.io/content/2-edge/tasks/exposing-dashboard.md +++ b/linkerd.io/content/2-edge/tasks/exposing-dashboard.md @@ -199,7 +199,7 @@ the dashboard rejects any request whose `Host` header is not `localhost`, `127.0.0.1` or the service name `web.linkerd-viz.svc`. Note that this protection also covers the -[Grafana dashboard](../reference/architecture/#grafana). +[Grafana dashboard](../features/dashboard/#grafana). The ingress-nginx config above uses the `nginx.ingress.kubernetes.io/upstream-vhost` annotation to properly set the diff --git a/linkerd.io/content/2-edge/tasks/setting-up-service-profiles.md b/linkerd.io/content/2-edge/tasks/setting-up-service-profiles.md index 0c15421ba4..8702326858 100644 --- a/linkerd.io/content/2-edge/tasks/setting-up-service-profiles.md +++ b/linkerd.io/content/2-edge/tasks/setting-up-service-profiles.md @@ -57,7 +57,7 @@ use the name `my-service.prod.svc.cluster.local` for the ServiceProfile. Note that at present, you cannot view statistics gathered for routes in this ServiceProfile in the web dashboard. You can get the statistics using the CLI. -For a complete demo walkthrough, check out the [books](books/#service-profiles) +For a complete demo walkthrough, check out the [books](books/) demo. There are a couple different ways to use `linkerd profile` to create service diff --git a/linkerd.io/content/2.19/reference/cli/viz.md b/linkerd.io/content/2.19/reference/cli/viz.md index da24ef2e19..e60d25f89b 100644 --- a/linkerd.io/content/2.19/reference/cli/viz.md +++ b/linkerd.io/content/2.19/reference/cli/viz.md @@ -40,7 +40,7 @@ title: viz {{< cli-description "viz dashboard" >}} -Check out the [architecture](../architecture/#dashboard) docs for a more +Check out the [dashboard](../../features/dashboard/#linkerd-dashboard) docs for a more thorough explanation of what this command does. {{< cli-examples "viz dashboard" >}} diff --git a/linkerd.io/content/2.19/tasks/exposing-dashboard.md b/linkerd.io/content/2.19/tasks/exposing-dashboard.md index 0f0d9ef682..3baa123db6 100644 --- a/linkerd.io/content/2.19/tasks/exposing-dashboard.md +++ b/linkerd.io/content/2.19/tasks/exposing-dashboard.md @@ -199,7 +199,7 @@ the dashboard rejects any request whose `Host` header is not `localhost`, `127.0.0.1` or the service name `web.linkerd-viz.svc`. Note that this protection also covers the -[Grafana dashboard](../reference/architecture/#grafana). +[Grafana dashboard](../features/dashboard/#grafana). The ingress-nginx config above uses the `nginx.ingress.kubernetes.io/upstream-vhost` annotation to properly set the diff --git a/linkerd.io/content/2.19/tasks/setting-up-service-profiles.md b/linkerd.io/content/2.19/tasks/setting-up-service-profiles.md index 0c15421ba4..8702326858 100644 --- a/linkerd.io/content/2.19/tasks/setting-up-service-profiles.md +++ b/linkerd.io/content/2.19/tasks/setting-up-service-profiles.md @@ -57,7 +57,7 @@ use the name `my-service.prod.svc.cluster.local` for the ServiceProfile. Note that at present, you cannot view statistics gathered for routes in this ServiceProfile in the web dashboard. You can get the statistics using the CLI. -For a complete demo walkthrough, check out the [books](books/#service-profiles) +For a complete demo walkthrough, check out the [books](books/) demo. There are a couple different ways to use `linkerd profile` to create service