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
{{ message }}
This repository has been archived by the owner on Dec 1, 2024. It is now read-only.
The current implementation of flotta's logging is done by watching a configmap.
When the log_level element of that map is changed, the pod is being restarted.
While this allows to apply new log verbosity level in all operators, there are less desired side-effects, such as
initializing the entire-cache (depends on the scale, can take sometime + introduce unnecessary load on etcd/api-server).
Using https://pkg.go.dev/go.uber.org/zap#AtomicLevel, the log verbosity could be changed on the fly.
We'd like to explore that approach and to minimize the restarted when can be avoided.
The text was updated successfully, but these errors were encountered:
The current implementation of flotta's logging is done by watching a configmap.
When the log_level element of that map is changed, the pod is being restarted.
While this allows to apply new log verbosity level in all operators, there are less desired side-effects, such as
initializing the entire-cache (depends on the scale, can take sometime + introduce unnecessary load on etcd/api-server).
Using https://pkg.go.dev/go.uber.org/zap#AtomicLevel, the log verbosity could be changed on the fly.
We'd like to explore that approach and to minimize the restarted when can be avoided.
The text was updated successfully, but these errors were encountered: