whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix mismatched hostnames in documentation (#12026)

Browse Source 
Match hostnames in description to example. `service2` in the description matches `second.foo.com` in the example.
This commit is contained in:
Fladrif
2019-01-08 04:10:02 -08:00
committed by Kubernetes Prow Robot
parent 4f189afac1
commit 5e96f9ad77
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/ingress.md
+1 -1
View File
@@ -294,7 +294,7 @@ spec:
If you create an ingress resource without any hosts defined in the rules, then any If you create an ingress resource without any hosts defined in the rules, then any
web traffic to the IP address of your ingress controller can be matched without a name based web traffic to the IP address of your ingress controller can be matched without a name based
virtual host being required. For example, the following ingress resource will route traffic virtual host being required. For example, the following ingress resource will route traffic
requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic requested for `first.bar.com` to `service1`, `second.foo.com` to `service2`, and any traffic
to the IP address without a hostname defined in request (that is, without a request header being to the IP address without a hostname defined in request (that is, without a request header being
presented) to `service3`. presented) to `service3`.