From 103600ce8d8e4b582ba5d54fae7b22f22ac0b383 Mon Sep 17 00:00:00 2001 From: Brian Avery Date: Thu, 13 Jun 2019 17:06:43 -0400 Subject: [PATCH] Updated traffic management to point to ingress docs (#4396) --- .../docs/tasks/traffic-management/tcp-traffic-shifting/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/tasks/traffic-management/tcp-traffic-shifting/index.md b/content/docs/tasks/traffic-management/tcp-traffic-shifting/index.md index b5a945de46..9d7078dff2 100644 --- a/content/docs/tasks/traffic-management/tcp-traffic-shifting/index.md +++ b/content/docs/tasks/traffic-management/tcp-traffic-shifting/index.md @@ -61,7 +61,7 @@ weighted routing feature. 1. Confirm that the `tcp-echo` service is up and running. The `$INGRESS_HOST` variable below is the External IP address of the ingress, as explained in -the [Bookinfo](/docs/examples/bookinfo/#determining-the-ingress-ip-and-port) doc. To obtain the +the [Ingress Gateways](/docs/tasks/traffic-management/ingress/ingress-control/#determining-the-ingress-ip-and-ports) doc. To obtain the `$INGRESS_PORT` value, use the following command. {{< text bash >}}