Details
-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.12
-
None
-
Moderate
-
No
-
False
-
Description
Description of problem:
Kube controller manage spams logs when cronjob concurrency is forbid. ------- I1106 18:44:59.972816 1 event.go:294] "Event occurred" object="ard-test/abctriage" fieldPath="" kind="CronJob" apiVersion="batch/v1" type="Normal" reason="JobAlreadyActive" message="Not starting job because prior execution is running and concurrency policy is Forbid" I1106 18:44:59.972824 1 event.go:294] "Event occurred" object="ard-test/abctriage" fieldPath="" kind="CronJob" apiVersion="batch/v1" type="Normal" reason="JobAlreadyActive" message="Not starting job because prior execution is running and concurrency policy is Forbid" I1106 18:44:59.972832 1 event.go:294] "Event occurred" object="ard-test/abctriage" fieldPath="" kind="CronJob" apiVersion="batch/v1" -------
Version-Release number of selected component (if applicable):
4.x
How reproducible:
Steps to Reproduce:
Actual results:
This creates a large amount of logs, which impacts customer's logging licensing as well as utilization of nodes.
Expected results:
Reduce excessive logging.
Additional info:
Excessive Logging from CronJob #118789 https://github.com/kubernetes/kubernetes/issues/118789
