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

Fix spelling (#6510)

This commit is contained in:
Eric Van Norman 2020-02-20 09:48:55 -06:00 committed by GitHub
parent fa2974c23a
commit ba89d40479
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tasks/traffic-management/ingress/ingress-control/index.md
View File

@ -190,7 +190,7 @@ Let's see how you can configure a `Gateway` on port 80 for HTTP traffic.
Internal requests from other services in the mesh are not subject to these rules Internal requests from other services in the mesh are not subject to these rules
but instead will default to round-robin routing. To apply these rules to internal calls as well, but instead will default to round-robin routing. To apply these rules to internal calls as well,
you can add the special value `mesh` to the list of `gateways`. Since the internal hostname for the you can add the special value `mesh` to the list of `gateways`. Since the internal hostname for the
service is probabaly different (e.g., `httpbin.default.svc.cluster.local`) from the external one, service is probably different (e.g., `httpbin.default.svc.cluster.local`) from the external one,
you will also need to add it to the `hosts` list. Refer to the you will also need to add it to the `hosts` list. Refer to the
[operations guide](/docs/ops/common-problems/network-issues#route-rules-have-no-effect-on-ingress-gateway-requests) [operations guide](/docs/ops/common-problems/network-issues#route-rules-have-no-effect-on-ingress-gateway-requests)
for more details. for more details.