ingress-nginx-helm/internal/ingress
Thomas Jackson 500b043f27 Don't use DNS resolution to "validate FQDN"
As the controller stands today this "validation" is done once per config load, which means if the DNS query fails for any reason the endpoint will remain dead until both (1) a change happens to the ingress and (2) the DNS resolution works. If the user configured the name we should just pass it through, this way the lua dns can attempt to re-query it at its leisure.
2019-10-13 13:16:47 -07:00
..
annotations Add support for configmap of headers to be sent to external auth service 2019-09-24 10:53:23 -04:00
controller Don't use DNS resolution to "validate FQDN" 2019-10-13 13:16:47 -07:00
defaults Lint code using staticcheck (#4471) 2019-08-23 12:08:40 -04:00
errors implement canary annotation and alternative backends 2018-11-06 13:13:14 -05:00
metric Refactor health checks and wait until NGINX process ends 2019-09-01 15:31:27 -04:00
resolver Add support for configmap of headers to be sent to external auth service 2019-09-24 10:53:23 -04:00
status Refactor ingress status IP address (#4490) 2019-08-25 12:27:34 -04:00
sslcert.go Allow multiple CA Certificates (#4556) 2019-09-13 09:22:24 -03:00
types.go Added new affinity mode for maximum session stickyness. Fixes kubernetes/ingress-nginx#4475 2019-08-30 11:40:29 +02:00
types_equals.go Merge pull request #4514 from alexmaret/4475-stickyness-mode 2019-09-24 05:09:27 -07:00
types_equals_test.go Fix broken test's filename 2019-07-26 18:15:25 -04:00
zz_generated.deepcopy.go Update generated code 2019-05-14 20:15:49 -04:00