ingress-nginx-helm/controllers/README.md
Peter Lee 0b6f4d2770 Minor text fix for "ApiServer"
It looks a little weird to apply camel case style for the noun "apiserver", i didn't see somewhere else spelling it in that way.
2017-03-04 00:40:07 +08:00

11 lines
996 B
Markdown

# Ingress controllers
This directory contains ingress controllers.
=======
# Ingress Controllers
Configuring a webserver or loadbalancer is harder than it should be. Most webserver configuration files are very similar. There are some applications that have weird little quirks that tend to throw a wrench in things, but for the most part you can apply the same logic to them and achieve a desired result. The Ingress resource embodies this idea, and an Ingress controller is meant to handle all the quirks associated with a specific "class" of Ingress (be it a single instance of a loadbalancer, or a more complicated setup of frontends that provide GSLB, DDoS protection etc).
## What is an Ingress Controller?
An Ingress Controller is a daemon, deployed as a Kubernetes Pod, that watches the apiserver's `/ingresses` endpoint for updates to the [Ingress resource](https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/ingress.md). Its job is to satisfy requests for ingress.