Add option to disable stack traces for zap logs --zap-stacktrace-level

[bharathi-tenneti]

Description:
Allow users to disable stacktraces , using --zap-stacktrace-level, when running the operator.

[vincepri]

You should be able to register the flag in your controller, like we do for klog. I'm not sure if there is anything for controller-runtime to do in this case.

[vincepri]

/priority awaiting-more-evidence
/milestone Next

[camilamacedo86]

@vincepri it is related to : #915 after merge this one we would be nice be allowed to disable/enable it.

[camilamacedo86]

Hi @vincepri,

For we You should be able to register the flag in your controller, like we do for klog. I'm not sure if there is anything for controller-runtime to do in this case. the user requires to do the change in the code, Am I right? If yes, I understand that the flag allows disable/enable the logs on the cluster where the project is running without code changes.

if I am wrong here, I think we can just add an example here how to do your suggestion and then close this one.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[croomes]

I had the same issue but I couldn't find a good way to disable stack traces completely. I checked klog but couldn't find anything relevant. Allowing the user to set panic as the --zap-stacktrace-level seems like a simple solution.

/remove-lifecycle stale