We want to be able to override the log level of KubeCarrier, so users can access debug or tracing level logs in order to troubleshoot issues. Users may also choose another log level to reduce the amount of logs KubeCarrier produces.
Component-level granularity of this setting is not strictly needed, but it would assist greatly in reducing the amount of extra logs that are generated when doing debug or tracing logs. And thus also prevents accidental congestion of the cluster log sink.
We want to be able to override the log level of KubeCarrier, so users can access debug or tracing level logs in order to troubleshoot issues. Users may also choose another log level to reduce the amount of logs KubeCarrier produces.
Component-level granularity of this setting is not strictly needed, but it would assist greatly in reducing the amount of extra logs that are generated when doing debug or tracing logs. And thus also prevents accidental congestion of the cluster log sink.