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
Those messages appear with every key stroke when typing in the pod shell. This might be irritating to new k8s users and they might think, something is broken. I did some research on the problem - it seems like others have the same problem and a lot of questions are unanswered as its not obvious to make this link.
It would be great if we could have an API option to toggle this behaviour rather than have it controlled via a global env var.
The current behaviour means that anything with transitive dependencies on this package spews cryptic debug messages to stderr if DEBUG is set in the environment, which is not very user-friendly.
smlx
added a commit
to uselagoon/lagoon-ssh-portal
that referenced
this issue
Feb 3, 2022
Problem: If one has
debug=True
set as environment variable, the logging behavior might be irritating using e.g. kubectl.It brings a bunch of messages - e.g. when using the shell of an pod:
Those messages appear with every key stroke when typing in the pod shell. This might be irritating to new k8s users and they might think, something is broken. I did some research on the problem - it seems like others have the same problem and a lot of questions are unanswered as its not obvious to make this link.
This was also posted in kubernetes/kubectl#1153 as I asked to change
kubectl
behavior.Proposed solution: Would it be possible, to change the env variable used to something other then
debug
?The text was updated successfully, but these errors were encountered: