You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/services-networking/ingress.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -485,9 +485,7 @@ web traffic to the IP address of your Ingress controller can be matched without
485
485
virtual host being required.
486
486
487
487
For example, the following Ingress routes traffic
488
-
requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic
489
-
to the IP address without a hostname defined in request (that is, without a request header being
490
-
presented) to `service3`.
488
+
requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic whose request host header doesn't match `first.bar.com` and `second.bar.com` to `service3`.
0 commit comments