From b0d9d76aa71dec00b61aef531fd1b0ee25f63459 Mon Sep 17 00:00:00 2001 From: Lee Calcote Date: Mon, 13 Mar 2017 22:20:42 -0500 Subject: [PATCH] Update README.md Changed "Ingerss" to "Ingress" --- docs/faq/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/README.md b/docs/faq/README.md index dd36de9a1..865921581 100644 --- a/docs/faq/README.md +++ b/docs/faq/README.md @@ -23,7 +23,7 @@ Table of Contents The Kubernetes Service is an abstraction over endpoints (pod-ip:port pairings). The Ingress is an abstraction over Services. This doesn't mean all Ingress controller must route *through* a Service, but rather, that routing, security -and auth configuration is represented in the Ingerss resource per Service, and +and auth configuration is represented in the Ingress resource per Service, and not per pod. As long as this configuration is respected, a given Ingress controller is free to route to the DNS name of a Service, the VIP, a NodePort, or directly to the Service's endpoints.