History

Fernando Diaz 0c178252b2 Correct Error Handling to avoid panics and add more logging to template When a type error is found we return an empty object of the expected type(Example: return "" for string return type). Also makes adds logging to all errors caused by type and corrects all related logging for consistency.		2017-09-22 18:12:08 -05:00
..
gce	default backend service quota now 5	2017-09-15 15:08:30 -04:00
nginx	Correct Error Handling to avoid panics and add more logging to template	2017-09-22 18:12:08 -05:00
README.md	cleanup controllers readme	2017-08-12 03:27:47 -04:00

README.md

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.