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
kubexit currently has multiple log.printf statements for informational logs arounds tombstones, birth deps, graveyards and death deps. Currently, these logs are indistinguishable from the logs of the command being run by kubexit which can cause a great deal of confusion and concern for users who see these logs mixed in with the logs of the command they wished to run.
Adding the ability to configure loglevel or adding a prefix so that the logs can be filtered out would be very helpful for operators.
kubexit currently has multiple log.printf statements for informational logs arounds tombstones, birth deps, graveyards and death deps. Currently, these logs are indistinguishable from the logs of the command being run by kubexit which can cause a great deal of confusion and concern for users who see these logs mixed in with the logs of the command they wished to run.
Adding the ability to configure loglevel or adding a prefix so that the logs can be filtered out would be very helpful for operators.
Example:
https://github.com/karlkfi/kubexit/blob/master/cmd/kubexit/main.go#L56
The text was updated successfully, but these errors were encountered: