ingress-nginx-helm/controllers
Manuel Alejandro de Brito Fontes 02cd3ce885 Merge pull request #225 from electroma/nginx/extauth_headers
Support for http header passing from external authentication service
2017-04-01 20:40:29 -03:00
..
gce Merge pull request #477 from nicksardo/glbc-service-watch 2017-03-22 13:08:30 -07:00
nginx Merge pull request #225 from electroma/nginx/extauth_headers 2017-04-01 20:40:29 -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.