Output from init container 'init-directories' logged at level ERROR. #701
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Running Gitea in Kubernetes (GKE), the output from the init-directories container is logged at severity ERROR. I believe that is incorrect, and the level should be INFO. Can I do a configuration change to address this, or does it need to be fixed in the chart itself?
I'm wondering why the output of the other init containers is not logged at level ERROR?
Example from the GKE GUI:
The script, init_directory_structure.sh, that is being run in the container, seems to be here:
036b469ff9/templates/gitea/init.yaml (L14)
It seems to me, that the problem might be with the set -x command used in the script. Someone is having a similar problem here: https://stackoverflow.com/questions/66815412/redirect-set-x-set-o-xtrace-to-standard-output
It looks to me like the set -x was added by @justusbunsi in this PR: https://gitea.com/gitea/helm-chart/pulls/178
Interesting! I didn't know this.
I think you're right,
set -x
is logging to stderr and hence you're seeing them logged as you described.@justusbunsi Are you ok with removing
set -x
in this case?I think
set -x
could be removed in this case, but perhaps some echo statements could be added in, so the progress of the script is still tracked.I'm happy to make a PR for that. Should I go ahead?
Yes, thanks!
My PR is ready for review: https://gitea.com/gitea/helm-chart/pulls/708