Update zap options to support specifying log level #308
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolved #305
Can check with this command
go run main.go -zap-log-level [level]
[flag] -zap-log-level value: Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
ref) https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/
By passing args to the spec part of deployment, the log level can be set.
e.g)
https://github.com/OT-CONTAINER-KIT/redis-operator/blob/master/config/manager/manager.yaml
At line 31