Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Logs are still written to file system (with logtostderr=true) #114

Open
wiegandf opened this issue Jun 25, 2020 · 0 comments
Open

Logs are still written to file system (with logtostderr=true) #114

wiegandf opened this issue Jun 25, 2020 · 0 comments

Comments

@wiegandf
Copy link

With logstderr set to true, there will still be some logs written to the filesystem. Eventrouter glog are correctly using stderr. I guess it is a dependency that writes the logs to /tmp folder:

W0625 06:04:16.385842       1 reflector.go:302] pkg/mod/k8s.io/[email protected]+incompatible/tools/cache/reflector.go:98: watch of *v1.Event ended with: The resourceVersion for the provided watch is too old.
log: exiting because of error: log: cannot create log: open /tmp/eventrouter.eventrouter-6b776f4cb9-jdwr4.unknownuser.log.WARNING.20200625-060416.1: not a directory

The above error happens in a custom distroless image. But I also verified the logs appear with the default eventrouter. Though, they can be written because /tmp folder exists.

wmfgerrit pushed a commit to wikimedia/operations-deployment-charts that referenced this issue Oct 26, 2020
* Add ingress NetworkPolicy and Prometheus annotations.
* Add config checksum to recreate pods on changes
* Add a emptyDir volume for /tmp to work arround Issue 114 [1]
* Add the option to overwrite kubernetes master/api environment
variables to work arround IP SAN limitation of puppet CA

[1] vmware-archive/eventrouter#114

Bug: T262675
Change-Id: Ia1632157971c6bee5eadb94be3ed81a058e64466
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant