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
we're currently using klog v2.3.0 and there is a known issue with --log_file_max_size minikube/klog option flag not working (being ignored), that was fixed in v2.4.0
in addition to fixing this bug, v2.4.0 introduced 2 new things:
one_output flag:
If true, only write logs to their native severity level (vs also writing to each lower severity level
LogFilter capabilities:
LogFilter is a collection of functions that can filter all logging calls, e.g. for sanitization of arguments and prevent accidental leaking of secrets.
and no other major changes
another interesting reason for upgrading to v2.4.0 is the release comment: Prepare release for Kubernetes v1.20
The text was updated successfully, but these errors were encountered:
we're currently using klog v2.3.0 and there is a known issue with
--log_file_max_size
minikube/klog option flag not working (being ignored), that was fixed in v2.4.0Steps to reproduce the issue:
minikube start --log_file='mqb.log' --log_file_max_size=3
result: the log file size will eventually grow over the set limit (3mb in this example)
ref: klog issue #171, pr #172
in addition to fixing this bug, v2.4.0 introduced 2 new things:
one_output
flag:LogFilter
capabilities:and no other major changes
another interesting reason for upgrading to v2.4.0 is the release comment: Prepare release for Kubernetes v1.20
The text was updated successfully, but these errors were encountered: