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 073241e341 Add more descriptive logging in certificate loading 
Currently a log "secret %v has no private key" is provided for
cert and "secret %v has no cert" is provided for key. They are in
the wrong place. This PR corrects the ordering and adds a
description as to what is actually missing.
2017-09-22 15:21:16 -05:00
..
gce Add more descriptive logging in certificate loading 2017-09-22 15:21:16 -05:00
nginx Add missing whitespace line between items 2017-09-19 13:25:07 -07:00
README.md cleanup controllers readme 2017-08-12 03:27:47 -04:00

README.md

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.