ingress-nginx-helm/controllers
Manuel de Brito Fontes e65d3c7571 Improve logs
2017-08-29 16:40:03 -03:00
..
gce Merge pull request #1181 from freehan/shared-informer 2017-08-28 16:50:05 -07:00
nginx Improve logs 2017-08-29 16:40:03 -03:00
README.md cleanup controllers readme 2017-08-12 03:27:47 -04:00

Ingress controllers

This directory contains 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 Ingresses.