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

Knobs to tune logging for network-operator #527

Open
adrianchiris opened this issue May 16, 2023 · 0 comments
Open

Knobs to tune logging for network-operator #527

adrianchiris opened this issue May 16, 2023 · 0 comments
Labels
enhancement New feature or request priority-medium

Comments

@adrianchiris
Copy link
Collaborator

adrianchiris commented May 16, 2023

What would you like to be added:

a way to configure log level for network operator and possibly its operands.
in a way that will not require a redeploy of the operator.

Why is this needed:

currently operator has zap-devel logging turned on, it is not structured and emits debug logs by default.
in production env we would most likey want INFO level logging as well as logs to be json encoded.

as for network operator operands, it may be a separate mechanism.
cluster disruption should be taken into account, which may mean we will not do it for the operands.
possiblitly: extend nicclusterpolicy per state with logLevel were applicable and let user decide.

@adrianchiris adrianchiris added the enhancement New feature or request label May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-medium
Projects
None yet
Development

No branches or pull requests

1 participant