ingress-nginx-helm/rootfs/etc/nginx/lua
Thomas Jackson b698699fdd More helpful DNS failure message
Previously if dns.lua failed to resolve a name you'd see the following in your logs:
```
2019/10/12 23:39:34 [error] 41#41: *6474 [lua] dns.lua:121: dns_lookup(): failed to query the DNS server:
server returned error code: 3: name error
server returned error code: 3: name error, context: ngx.timer
```

Unfortunately this doesn't tell you what name is failing (so you have to start guessing). To alleviate the pain this simply adds the host name we are attempting to resolve to the log line so users don't have to guess.
2019-10-14 08:14:35 -07:00
..
balancer Fixed LUA lint findings. 2019-09-24 10:56:11 +02:00
plugins/hello_world lua plugin system 2019-04-04 09:25:22 -04:00
test improve certificate configuration detection per request 2019-09-24 21:17:22 -04:00
util More helpful DNS failure message 2019-10-14 08:14:35 -07:00
balancer.lua optimize: local cache global variable and reduce string object creation. 2019-09-25 09:43:11 -04:00
certificate.lua improve certificate configuration detection per request 2019-09-24 21:17:22 -04:00
configuration.lua cleanup unused certificates 2019-09-24 14:16:03 -04:00
lua_ingress.lua improve certificate configuration detection per request 2019-09-24 21:17:22 -04:00
monitor.lua use nkeys for counting lua table elements 2019-05-26 18:15:15 -04:00
plugins.lua lua plugin system 2019-04-04 09:25:22 -04:00
tcp_udp_balancer.lua teach lua about search and ndots settings in resolv.conf 2019-08-14 18:03:30 -04:00
tcp_udp_configuration.lua Fix DNS failures in L4 services 2019-02-17 14:12:10 -08:00
util.lua optimize: local cache global variable and avoid single lines over 80 2019-09-24 10:08:45 -04:00