DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source 
Changed "Ingerss" to "Ingress"
This commit is contained in:
Lee Calcote 2017-03-13 22:20:42 -05:00 committed by GitHub
parent 5b25f7de5c
commit 8df25b771a
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/faq/README.md
View file

@ -23,7 +23,7 @@ Table of Contents
The Kubernetes Service is an abstraction over endpoints (pod-ip:port pairings). 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 The Ingress is an abstraction over Services. This doesn't mean all Ingress
controller must route *through* a Service, but rather, that routing, security 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 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, controller is free to route to the DNS name of a Service, the VIP, a NodePort,
or directly to the Service's endpoints. or directly to the Service's endpoints.