History

Bob Van Zant 045cceacac Use nginx default value for SSLECDHCurve This configuration setting permits nginx to auto discover supported curves based on what openssl was compiled with. With the old default of secp384r1 if you attempted to use a key from a different curve, for example prime256v1, the SSL handshake would fail in an awful way without any helpful errors logged anywhere. The default setting in nginx has been "auto" since 1.11.0		2017-09-21 11:56:52 -07:00
..
gce	default backend service quota now 5	2017-09-15 15:08:30 -04:00
nginx	Use nginx default value for SSLECDHCurve	2017-09-21 11:56:52 -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.