Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to change log level ? #692

Open
necipakca opened this issue Dec 26, 2021 · 5 comments
Open

How to change log level ? #692

necipakca opened this issue Dec 26, 2021 · 5 comments

Comments

@necipakca
Copy link

I could not find and information about change log level of operator.
Currently it is comes with DEBUG level and it produces insane logs which is I do not need.

@papi83dm
Copy link

papi83dm commented Feb 4, 2022

@necipakca did you figure out how to do this?

@necipakca
Copy link
Author

Nope :) I have excluded Jenkins operator logs from fluent-bit.

@chrisgrove-keysight
Copy link

I remembered the tidbit Jenkins Kubernetes Operator uses the Operator SDK and found the logging documention
https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/

We use separate namespaces for Jenkins and the operator so it was trivial to add the --zap-log-level=info to the args list. The logging level is now back to sane.

- command: - /manager args: - --leader-elect - --zap-log-level=info image: virtuslab/jenkins-operator:29c5b1e name: jenkins-operator

@papi83dm
Copy link

papi83dm commented Mar 1, 2022

@chrisgrove-keysight Thanks, However the helm chart does not support passing custom args.

https://github.com/jenkinsci/kubernetes-operator/blob/master/chart/jenkins-operator/templates/operator.yaml#L34

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this issue is still affecting you, just comment with any updates and we'll keep it open. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@brokenpip3 brokenpip3 added this to the 0.9 milestone Mar 7, 2023
@stale stale bot removed the stale label Mar 7, 2023
@github-actions github-actions bot added the stale label May 8, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
@brokenpip3 brokenpip3 reopened this May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants