Skip to content

Commit a30f812

Browse files
committed
fix link
Signed-off-by: Alec Rajeev <ccarajeev342@gmail.com>
1 parent 4d40e73 commit a30f812

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • docs/features/traffic-management

docs/features/traffic-management/alb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ spec:
138138
By default, a rollout will inject the `alb.ingress.kubernetes.io/actions.<SERVICE-NAME>` annotation
139139
using the service/action name specified under `spec.strategy.canary.stableService`. However, it may
140140
be desirable to specify an explicit service/action name different from the `stableService`. For
141-
example, [one pattern](/best-practices/#ingress-desiredstable-host-routes) is to use a single
141+
example, [one pattern](/argo-rollouts/best-practices/#ingress-desiredstable-host-routes) is to use a single
142142
Ingress containing three different rules to reach the canary, stable, and root service separately
143143
(e.g. for testing purposes). In this case, you may want to specify a "root" service as the
144144
service/action name instead of stable. To do so, reference a service under `rootService` under the

0 commit comments

Comments
 (0)