DevFW-CICD/ingress-nginx-helm
12
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ingress-nginx-helm/controllers
History
Fernando Diaz e12138f4dc Remove any aliases that conflict with a hostname 
Removes the alias association if an existing server
with the same hostname as the alias exists. This is
done to disallow any duplicate server creation when
the alias annotation is provided.
2017-08-17 13:05:52 -05:00
..
gce Fix some broken link 2017-08-08 17:50:14 +08:00
nginx Remove any aliases that conflict with a hostname 2017-08-17 13:05:52 -05:00
README.md Update outdated ingress resource link 2017-06-22 17:30:59 -07: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.