From 795c418633525760bb5b3e3f5ad3c36e4ebe9183 Mon Sep 17 00:00:00 2001 From: Joost Hietbrink Date: Wed, 28 Nov 2018 16:46:01 +0100 Subject: [PATCH] Updated ingress.md (#11213) Typo serivceName. --- content/en/docs/concepts/services-networking/ingress.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index b6d52c63760..8b5638939c4 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -136,10 +136,10 @@ for directing HTTP traffic. Each http rule contains the following information: -* An optional host. In this example, no host is specified, so the rule will apply to all inbound - HTTP traffic through the IP address that will be connected. If a host is provided, for example: - foo.bar.com, the rules will apply on to that host. -* a list of paths (e.g.: /testpath) each of which has an associated backend defined with a `serviceName` +* An optional host. In this example, no host is specified, so the rule applies to all inbound + HTTP traffic through the IP address is specified. If a host is provided (for example, + foo.bar.com), the rules apply to that host. +* a list of paths (for example, /testpath), each of which has an associated backend defined with a `serviceName` and `servicePort`. Both the host and path must match the content of an incoming request before the loadbalancer will direct traffic to the referenced service. * A backend is a combination of service and port names as described in the