Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix TO logging configuration when deployed by the CO #10899

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

scholzj
Copy link
Member

@scholzj scholzj commented Dec 3, 2024

Type of change

  • Bugfix

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

  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally

@scholzj scholzj added this to the 0.45.0 milestone Dec 3, 2024
@scholzj scholzj requested a review from ppatierno December 3, 2024 11:04
@scholzj
Copy link
Member Author

scholzj commented Dec 3, 2024

/azp run regression

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj scholzj merged commit 3a91777 into strimzi:main Dec 4, 2024
21 checks passed
@scholzj scholzj deleted the fix-TO-logging-configuration branch December 4, 2024 09:17
OwenCorrigan76 pushed a commit to OwenCorrigan76/strimzi-kafka-operator that referenced this pull request Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants