From 5e96f9ad77665eade70eec3b19af0aa8f65a81e9 Mon Sep 17 00:00:00 2001 From: Fladrif Date: Tue, 8 Jan 2019 04:10:02 -0800 Subject: [PATCH] Fix mismatched hostnames in documentation (#12026) Match hostnames in description to example. `service2` in the description matches `second.foo.com` in the example. --- content/en/docs/concepts/services-networking/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index 8b5638939c..6b6896c44b 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -294,7 +294,7 @@ spec: 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 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 presented) to `service3`.