From 5b1d11e489fe4fdac4e99f20c68dc47b8641d087 Mon Sep 17 00:00:00 2001
From: Frank Budinsky <frankb@ca.ibm.com>
Date: Thu, 16 May 2019 12:42:34 -0400
Subject: [PATCH] Clarifications (#4145)

---
 .../docs/tasks/traffic-management/egress/index.md   | 13 +------------
 .../docs/tasks/traffic-management/ingress/index.md  |  5 ++++-
 2 files changed, 5 insertions(+), 13 deletions(-)

diff --git a/content/docs/tasks/traffic-management/egress/index.md b/content/docs/tasks/traffic-management/egress/index.md
index ad39dbf72c..e45539f326 100644
--- a/content/docs/tasks/traffic-management/egress/index.md
+++ b/content/docs/tasks/traffic-management/egress/index.md
@@ -23,17 +23,6 @@ This task shows you how to access external services in three different ways:
 
 *   Setup Istio by following the instructions in the [Installation guide](/docs/setup/).
 
-    {{< warning >}}
-    If the following [installation options](/docs/reference/config/installation-options/) are not configured
-    in your selected [configuration profile](/docs/setup/kubernetes/additional-setup/config-profiles/),
-    add them with the following values:
-
-    {{< text plain >}}
-    --set global.outboundTrafficPolicy.mode=ALLOW_ANY --set pilot.env.PILOT_ENABLE_FALLTHROUGH_ROUTE=1
-    {{< /text >}}
-
-    {{< /warning >}}
-
 *   Deploy the [sleep]({{< github_tree >}}/samples/sleep) sample app to use as a test source for sending requests.
     If you have
     [automatic sidecar injection](/docs/setup/kubernetes/additional-setup/sidecar-injection/#automatic-sidecar-injection)
@@ -72,7 +61,7 @@ without controlling access to external services.
 You can then decide to [configure access to external services](#controlled-access-to-external-services) later.
 
 {{< warning >}}
-In versions prior to Istio 1.1.3, `ALLOW_ANY` only worked on ports with no HTTP services or
+In versions prior to Istio 1.1.4, `ALLOW_ANY` only worked on ports with no HTTP services or
 service entries defined within the mesh.
 External hosts using the same port as any internal HTTP service
 fell back to a blocking-by-default behavior.
diff --git a/content/docs/tasks/traffic-management/ingress/index.md b/content/docs/tasks/traffic-management/ingress/index.md
index 829469b38e..71251cfee4 100644
--- a/content/docs/tasks/traffic-management/ingress/index.md
+++ b/content/docs/tasks/traffic-management/ingress/index.md
@@ -53,7 +53,8 @@ $ export INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway
 $ export SECURE_INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="https")].port}')
 {{< /text >}}
 
-Note that in certain environments, the load balancer may be exposed using a host name, instead of an IP address.
+{{< warning >}}
+In certain environments, the load balancer may be exposed using a host name, instead of an IP address.
 In this case, the `EXTERNAL-IP` value in the output from the command in the previous section will not be an IP address,
 but rather a host name, and the above command will have failed to set the `INGRESS_HOST` environment variable. In this case, use the following command to correct the `INGRESS_HOST` value:
 
@@ -61,6 +62,8 @@ but rather a host name, and the above command will have failed to set the `INGRE
 $ export INGRESS_HOST=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
 {{< /text >}}
 
+{{< /warning >}}
+
 #### Determining the ingress IP and ports when using a node port
 
 Follow these instructions if you have determined that your environment **does not have** an external load balancer.