Skip to content

Commit

Permalink
Fix broken links (kubernetes#1066)
Browse files Browse the repository at this point in the history
* Fix broken links
* fix lint

Signed-off-by: Charles Pretzer <charles@buoyant.io>
  • Loading branch information
cpretzer authored May 5, 2021
1 parent 0e0359a commit 725bbab
Show file tree
Hide file tree
Showing 8 changed files with 8 additions and 8 deletions.
2 changes: 1 addition & 1 deletion linkerd.io/content/2.10/features/ha.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ Prometheus and Grafana.
The Linkerd Viz extension provides a pre-configured Prometheus pod, but for
production workloads we recommend setting up your own Prometheus instance. To
scrape the data plane metrics, follow the instructions
[here](https://linkerd.io../../tasks/external-prometheus/). This will provide you
[here](../../tasks/external-prometheus/). This will provide you
with more control over resource requirement, backup strategy and data retention.

When planning for memory capacity to store Linkerd timeseries data, the usual
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.10/tasks/installing-multicluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -360,4 +360,4 @@ The same functionality can also be done through Helm setting the

Now that the multicluster components are installed, operations like linking, etc
can be performed by using the linkerd CLI's multicluster sub-command as per the
[multicluster task](https://linkerd.io../../features/multicluster).
[multicluster task](../../features/multicluster/).
2 changes: 1 addition & 1 deletion linkerd.io/content/2.10/tasks/using-ingress.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ can be run with your Ingress Controller.

When the ingress controller is injected with the `linkerd.io/inject: enabled`
annotation, the Linkerd proxy will honor load balancing decisions made by the
ingress controller instead of applying [its own EWMA load balancing](https://linkerd.io../../features/load-balancing/).
ingress controller instead of applying [its own EWMA load balancing](../../features/load-balancing/).
This also means that the Linkerd proxy will not use Service Profiles for this
traffic and therefore will not expose per-route metrics or do traffic splitting.

Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.10/tasks/using-the-debug-container.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ incoming and outgoing traffic with `tshark`, which can then be viewed with
container and run commands directly.

For instance, if you've gone through the [Linkerd Getting
Started](https://linkerd.io../../getting-started/) guide and installed the
Started](../../getting-started/) guide and installed the
*emojivoto* application, and wish to debug traffic to the *voting* service, you
could run:

Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.9/features/ha.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ Prometheus and Grafana.

For production workloads, we recommend setting up your own Prometheus instance
to scrape the data plane metrics, following the instructions
[here](https://linkerd.io../../tasks/external-prometheus/). This will provide you
[here](../../tasks/external-prometheus/). This will provide you
with more control over resource requirement, backup strategy and data retention.

When planning for memory capacity to store Linkerd timeseries data, the usual
Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.9/tasks/installing-multicluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -358,4 +358,4 @@ The same functionality can also be done through Helm setting the

Now that the multicluster components are installed, operations like linking, etc
can be performed by using the linkerd CLI's multicluster sub-command as per the
[multicluster task](https://linkerd.io../../features/multicluster).
[multicluster task](../../features/multicluster/).
2 changes: 1 addition & 1 deletion linkerd.io/content/2.9/tasks/using-ingress.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ can be run with your Ingress Controller.

When the ingress controller is injected with the `linkerd.io/inject: enabled`
annotation, the Linkerd proxy will honor load balancing decisions made by the
ingress controller instead of applying [its own EWMA load balancing](https://linkerd.io../../features/load-balancing/).
ingress controller instead of applying [its own EWMA load balancing](../../features/load-balancing/).
This also means that the Linkerd proxy will not use Service Profiles for this
traffic and therefore will not expose per-route metrics or do traffic splitting.

Expand Down
2 changes: 1 addition & 1 deletion linkerd.io/content/2.9/tasks/using-the-debug-container.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ incoming and outgoing traffic with `tshark`, which can then be viewed with
container and run commands directly.

For instance, if you've gone through the [Linkerd Getting
Started](https://linkerd.io../../getting-started/) guide and installed the
Started](../../getting-started/) guide and installed the
*emojivoto* application, and wish to debug traffic to the *voting* service, you
could run:

Expand Down

0 comments on commit 725bbab

Please sign in to comment.