ingress-nginx-helm/controllers
Nick Sardo 14054be571 [GLBC] Fix problem surfacing error (#658)
* use syncError in defer GC

* surface other err as well
2017-04-26 15:30:33 -07:00
..
gce [GLBC] Fix problem surfacing error (#658) 2017-04-26 15:30:33 -07:00
nginx Merge pull request #637 from aledbf/0.9.0-beta.4 2017-04-25 18:10:16 -03:00
README.md Minor text fix for "ApiServer" 2017-03-04 00:40:07 +08: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.