Description
Regular process execution or stdio produces info log entries which clutter the log.
Steps to reproduce the issue:
- Run a K8s cluster based on the containerd CRI plugin with, e.g., Calico Pods running
- Observe many
info log entries related to process execution or stdout usage
Describe the results you received:
Jan 06 10:30:14 … env[651820]: time="2021-01-06T10:30:14.362567914Z" level=info msg="Finish piping \"stdout\" of container exec \"…\""
Jan 06 10:30:14 … env[651820]: time="2021-01-06T10:30:14.362698496Z" level=info msg="Finish piping \"stderr\" of container exec \"…\""
Jan 06 10:30:14 … env[651820]: time="2021-01-06T10:30:14.362728170Z" level=info msg="Exec process \"… exits with exit code 0 and error <nil>"
Jan 06 10:30:14 … env[651820]: time="2021-01-06T10:30:14.364023266Z" level=info msg="ExecSync for \"…\" returns with exit code 0"
Jan 06 10:30:15 … env[651820]: time="2021-01-06T10:30:15.343479617Z" level=info msg="ExecSync for \"…\" with command [/bin/calico-node -felix-ready -bird-ready] and timeout 1 (s)"
Jan 06 10:30:15 … env[651820]: time="2021-01-06T10:30:15.487156716Z" level=info msg="Finish piping \"stderr\" of container exec \"…\""
Jan 06 10:30:15 … env[651820]: time="2021-01-06T10:30:15.487198617Z" level=info msg="Finish piping \"stdout\" of container exec \"…\""
Jan 06 10:30:15 … env[651820]: time="2021-01-06T10:30:15.487347749Z" level=info msg="Exec process \"…\" exits with exit code 0 and error <nil>"
Jan 06 10:30:15 … env[651820]: time="2021-01-06T10:30:15.488674790Z" level=info msg="ExecSync for \"…\" returns with exit code 0"
Describe the results you expected:
All these entries should probably be logged under the debug log level which is not the default.
Output of containerd --version:
Any other relevant information:
Description
Regular process execution or stdio produces
infolog entries which clutter the log.Steps to reproduce the issue:
infolog entries related to process execution or stdout usageDescribe the results you received:
Describe the results you expected:
All these entries should probably be logged under the
debuglog level which is not the default.Output of
containerd --version:Any other relevant information: