feat(helm): allow to set log level in operator and controller #1850
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm waiting for the PR #1849 to be released, so I update the image version as well in this PR. |
carlosrodfern
force-pushed
the
set-operator-loglevel
branch
from
ccfb0c6
to
3461707
Compare
|
This is ready for review. |
carlosrodfern
force-pushed
the
set-operator-loglevel
branch
2 times, most recently
from
f73cc80
to
45e61f7
Compare
carlosrodfern
changed the title
|
@DelusionalOptimist: this PR would allow users to set the log levels which is related with the issue #1566 |
carlosrodfern
force-pushed
the
set-operator-loglevel
branch
from
45e61f7
to
44ccbd1
Compare
Fixes: kubearmor#1566 Signed-off-by: Carlos Rodriguez-Fernandez <[email protected]>
carlosrodfern
force-pushed
the
set-operator-loglevel
branch
from
44ccbd1
to
5be1942
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose of PR?:
Allow to set the log level for the operator in the helm chart values
Does this PR introduce a breaking change? No
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
This is to be able to use the log level feature added in this PR: #1849
Checklist:
<type>(<scope>): <subject>