How to change the log level of tf-job-operator

[chansonzhang]

Problem: tf-job-operator produced too many logs, and quickly filled up the disk.

I login to the tf-job-operator pod use kubectl exec -it <tf-job-operator-xxx>. And /opt/kubeflow/tf-operator.v1 --help shows that the parameter -v is the log level for V logs. But I can't found any document can tell me what the value of this parameter really mean. As we use the kubeflow version 0.7, the initial start option is -v=1, I then tried to change it to 0,2,3,4,5 but none of them took effect.

Then I read the source code, found that the -v option is not included in ServerOption definition

What I want: Can anyone kindly tell me how can I change the log level of tf-job-operator or any way can limit the log size. Thanks.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
kind/question	0.62

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[gaocegege]

We are using glog, and -v is supported by glog by default.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
area/tfjob	0.77

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.