From ce6da11e11a9f36438cedf361335f68de21b5146 Mon Sep 17 00:00:00 2001 From: Peter Lee Date: Tue, 3 Jan 2017 10:24:54 +0800 Subject: [PATCH] fix typo 'ips' should be 'IPs' --- docs/user-guide/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index e0bebc4795..b9c371e2a1 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -107,7 +107,7 @@ Where `107.178.254.228` is the IP allocated by the Ingress controller to satisfy ### Simple fanout -As described previously, pods within kubernetes have ips only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancer/s. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: +As described previously, pods within kubernetes have IPs only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancer/s. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like: ```shell foo.bar.com -> 178.91.123.132 -> / foo s1:80