Description
Description
Not sure if this should be a bug or a feature, please change it if needed.
I have deployed Gitea into a Kubernetes cluster using the Helm chart, in rootless mode.
I can see in the logs loooooads of SSH things. Read this issue to understand more and it has some links to fixes and stuff.
However, it looks like the SSH_LOG_LEVEL is not configurable when using a rootless image.
This is made apparent by the Gitea Helm chart templates which include conditionals to omit the environment variable when using rootless mode.
I also tried explicitly setting this envVar using:
deployment:
env:
- name: SSH_LOG_LEVEL
value: ERROR
and I can see the envVar is set in the Gitea container, but my guess is that it doesn't do anything within the app.ini or something similar.
@TheFox0x7 was on hand in the Discord channels to explain to me that this is an OpenSSH setting, and so therefore it is not applicable to the built-in SSH server that is used when running the rootless image.
I still think SSH_LOG_LEVEL should affect the logging of the built-in SSH server though and it would enable me to get rid of the SSH log spamming that I have without needing to use the root image or disable SSH logging completely.
Gitea Version
1.23.8
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.47.2
Operating System
Amazon Linux 2
How are you running Gitea?
Installed Gitea using the Helm chart onto an AWS EKS cluster.
Database
PostgreSQL