You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
klog (the glog fork used by kubernetes) commits suicide when trying to write an error
log: exiting because of error: log: cannot create log: open /tmp/controller.sealed-secrets-controller-665d687cc6-kjgl5.unknownuser.log.ERROR.20190725-153353.1: read-only file system
The text was updated successfully, but these errors were encountered:
Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.
Let's mount a writable `/tmp` dir.
Closes#200
Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.
Let's mount a writable `/tmp` dir.
Closes#200
202: Writable /tmp r=mkmik a=mkmik
Our deployment template uses the `readOnlyRootFilesystem` but the k8s `klog` library
likes to write logs in `/tmp`.
Let's mount a writable `/tmp` dir.
Closes#200
Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
klog
(the glog fork used by kubernetes) commits suicide when trying to write an errorThe text was updated successfully, but these errors were encountered: