ingress-nginx-helm/controllers
Nick Sardo d662620eff Merge pull request #1463 from nikhiljindal/refactorBackendSync
GCE: Updating instance groups interface to accept all named ports at once
2017-10-05 18:15:13 -07:00
..
gce Updating instances interface to accept all named ports at once 2017-10-05 17:44:43 -07:00
nginx Merge pull request #1478 from aledbf/rd 2017-10-05 13:58:58 -04: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.