Fix TO logging configuration when deployed by the CO #10899
Merged
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.
Type of change
Description
The default logging configuration pattern of the Topic Operator when deployed through the
Kafka
CR is currently for some reason different from the one used by CO and UO - but also from the pattern used by TO when deployed as a standalone operator.It also contains some leftover logging configuration from the bidirectional Topic Operator such as configuration for the Streams API classes etc. This is not needed anymore and is removed.
Checklist