istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix wildcard example description (#2901) 

* Fix wildcard example description

* Fix broken link
This commit is contained in:
Frank Budinsky 2018-11-19 13:37:35 -05:00 committed by GitHub
parent 830629db39
commit fdb69a2da3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/blog/2018/egress-mongo/index.md
View File

@ -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

2
content/docs/examples/advanced-gateways/wildcard-egress-hosts/index.md
View File

@ -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
---