As a tool maintainer
I want stderr/stdout from some jobs to be captured by Kubernetes
So that I can view the most recent log output using kubectl logs <pod-name> and avoid worrying about any file rotation and truncation issues for logs that are not highly useful as filesystem artifacts.
It appears that using the --no-filelog flag redirects both stdout and stderr to /dev/null. Based on the flag name I was instead expecting stdout and stderr to go to the default streams which are captured by Kubernetes. I would like to be able to specify this behavior with some combination of flag(s).