Allow users to specify the location of accesslogs about nghttpx-ingress-lb HOT 4 CLOSED

You can specify the location of access log file via ConfigMap.
https://github.com/zlabjp/nghttpx-ingress-lb#custom-nghttpx-configuration

For example, you can create following ConfigMap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: nghttpx-ingress-lb
data:
  nghttpx-conf: |
    accesslog-file=/path/to/access.log

And then pass --nghttpx-configmap=default/nghttpx-ingress-lb to the nghttpx ingress controller.
The controller finds ConfigMap, and configures nghttpx so that it writes access log to /path/to/access.log.

from nghttpx-ingress-lb.

I've already tried that method, it results in the following nghttpx configuration file:

accesslog-file=/dev/stdout

< omitted >

# from ConfigMap
 log-level=ERROR
 accesslog-file=/dev/null

However, because the second accesslog-file=/dev/null is appended to the bottom of the file, it doesn't seem to overwrite the first one, and thus the logs are being printed to stdout.

from nghttpx-ingress-lb.

It works for me. It should override the first one.
I'm a bit curious about the preceding white space in your configuration file:

# from ConfigMap
 log-level=ERROR
 accesslog-file=/dev/null

It should be:

# from ConfigMap

log-level=ERROR
accesslog-file=/dev/null

nghttpx complains against those white space characters, and refuses to reload the configuration.

from nghttpx-ingress-lb.

I think this works, but if it doesn't, please reopen this issue.

from nghttpx-ingress-lb.