From fdb69a2da3af30901047befd314d0d1ac5477d43 Mon Sep 17 00:00:00 2001 From: Frank Budinsky Date: Mon, 19 Nov 2018 13:37:35 -0500 Subject: [PATCH] Fix wildcard example description (#2901) * Fix wildcard example description * Fix broken link --- content/blog/2018/egress-mongo/index.md | 2 +- .../examples/advanced-gateways/wildcard-egress-hosts/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/blog/2018/egress-mongo/index.md b/content/blog/2018/egress-mongo/index.md index 663c9c39e1..fbcd775a24 100644 --- a/content/blog/2018/egress-mongo/index.md +++ b/content/blog/2018/egress-mongo/index.md @@ -780,7 +780,7 @@ You can pick a wildcarded domain according to your MongoDB host. To configure egress gateway traffic for a wildcarded domain, you will first need to deploy a custom egress gateway with -[an additional SNI proxy](/docs/examples/advanced-gateways/wildcard-https-egress-gateway/#https-traffic-to-arbitrary-wildcarded-domains). +[an additional SNI proxy](/docs/examples/advanced-gateways/wildcard-egress-hosts/#wildcard-configuration-for-arbitrary-domains). This is needed due to current limitations of Envoy, the proxy used by the standard Istio egress gateway. #### Prepare a new egress gateway with an SNI proxy diff --git a/content/docs/examples/advanced-gateways/wildcard-egress-hosts/index.md b/content/docs/examples/advanced-gateways/wildcard-egress-hosts/index.md index 736e1bf376..24574a5b9f 100644 --- a/content/docs/examples/advanced-gateways/wildcard-egress-hosts/index.md +++ b/content/docs/examples/advanced-gateways/wildcard-egress-hosts/index.md @@ -1,6 +1,6 @@ --- title: Configure Egress Traffic using Wildcard Hosts -description: Use an SNI proxy in addition to the Envoy instance in the istio-egressgateway for wildcarded domains. +description: Describes how to enable egress traffic for a set of hosts in a common domain, instead of configuring each and every host separately. keywords: [traffic-management,egress] weight: 50 ---