How are Kong logs stored when running in a Kubernetes cluster and were does it stores?

Kubernetes
1

"Hi, when I was using Kong with Helm, I noticed these lines:

proxy_access_log: /dev/stdout
admin_access_log: /dev/stdout
admin_gui_access_log: /dev/stdout
portal_api_access_log: /dev/stdout
proxy_error_log: /dev/stderr
admin_error_log: /dev/stderr
admin_gui_error_log: /dev/stderr
portal_api_error_log: /dev/stderr
prefix: /kong_prefix/
Are these the locations where Kong stores its logs, and does it require an enterprise version for this to work?"

2

@Abhin_23 - This means that the logs are being sent to STDOUT and STDERR which is the default location for logs. This does not require an enterprise license.

You can find them using

kubectl logs pod-id -n namespace

If you exec into the pod - you can find it here. It won’t be written to a file but rather redirected

lrwxrwxrwx  1 kong kong   11 Nov 25 08:12 access.log -> /dev/stdout
lrwxrwxrwx  1 kong kong   11 Nov 25 08:12 admin_access.log -> /dev/stdout
lrwxrwxrwx  1 kong kong   11 Nov 25 08:12 error.log -> /dev/stderr