ingress-nginx-helm/controllers
Manuel Alejandro de Brito Fontes a56dd7cc38 Merge pull request #1013 from caiyixiang/unify_forms
The fields of vtsDate are unified in the form of plural
2017-07-26 22:39:08 -04:00
..
gce adapt gce controller to godep updates 2017-07-25 17:09:27 -07:00
nginx Merge pull request #1013 from caiyixiang/unify_forms 2017-07-26 22:39:08 -04:00
README.md Update outdated ingress resource link 2017-06-22 17:30:59 -07: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.