README: explain how logs are meant to be used #56
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.
As the author of an issuer, I am unsure as to what log level to use, and whether I should be using Zap or Klog so that the log lines coming from my controller and the ones from issuer-lib are consistent.
For example, when my controller shows "The Issuer failed issuing", I'd like issuer-lib to show "Succeeded issuing" at the same log level.