ingress-nginx-helm/controllers
Prashanth B cb60085b17 Merge pull request #299 from bprashanth/owners
Add more assignees and approvers
2017-02-18 04:17:39 +05:30
..
gce Add more assignees and approvers 2017-02-17 10:47:56 -08:00
nginx Change nginx variable to use in filter of access_log 2017-02-17 18:21:46 -03:00
README.md Remove nginx-alpha, examples and simplify read files 2016-11-10 18:46:41 -03:00

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. Its job is to satisfy requests for ingress.