instruction for changing log level #35
Merged
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
tinaselenge
reviewed
Nov 11, 2024
| ``` | ||
| Note:<br> | ||
| (1) Set `podSecurityContext` to null so that we can run in OpenShift environment<br> | ||
| (2) Set `monitorInterval` to log4j properties file so that we can dynamically change log level for operator and job/task manager. |
There was a problem hiding this comment.
The monitorInterval is also only for Openshift environment?
There was a problem hiding this comment.
No, it's the property for log4j, not related to the running env.
tinaselenge
approved these changes
Nov 11, 2024
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.
Added commands/examples to instruct users how to change log level dynamically.