History

Martin Stiborsky beb17f39ab fixed lua_package_path in nginx.tmpl I did my own build of the nginx-ingress-controller and its docker image, but I had troubles with the `error_page.lua` module, which couldn't be loaded, there was an error in the log, module was not found. I think the lua package path is wrong, here is a fix.		2017-04-11 09:43:33 +02:00
..
gce	Rename packages from api to api_v1	2017-04-06 22:27:50 -07:00
nginx	fixed lua_package_path in nginx.tmpl	2017-04-11 09:43:33 +02:00
README.md	Minor text fix for "ApiServer"	2017-03-04 00:40:07 +08:00

README.md

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.