We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
2 parents 7706f6f + 991b35f commit b74478cCopy full SHA for b74478c
content/en/docs/concepts/services-networking/ingress.md
@@ -378,7 +378,7 @@ web traffic to the IP address of your Ingress controller can be matched without
378
virtual host being required.
379
380
For example, the following Ingress routes traffic
381
-requested for `first.bar.com` to `service1`, `second.foo.com` to `service2`, and any traffic
+requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic
382
to the IP address without a hostname defined in request (that is, without a request header being
383
presented) to `service3`.
384
0 commit comments