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 otel collector restart #16517
Fix otel collector restart #16517
Conversation
✅ Deploy Preview for kyma-project-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/retest |
/hold |
88548d5
to
3537cee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to add a unit test to cover this scenario?
Absolutely, planning to do that. |
/unhold |
@chrkl: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest |
* Fix otel collector restart * Bump telemetry-operator image * Enhance unittest for merging pod annotations
* Fix otel collector restart (#16517) * Fix otel collector restart * Bump telemetry-operator image * Enhance unittest for merging pod annotations * Bump telemetry-operator image
Description
Restarting the telemetry-trace-collector pod after the TracePipeline has changed is triggered by adding a configuration hash annotation to the Pod template. The way how
kubectl.kubernetes.io
prefixed annotations were merged from an existing deployment caused this annotation to be dropped and the collector was never restarted due to a configuration change.This PR ensures fixes merging existing Pod annotations with the newly applied ones.
Changes proposed in this pull request:
Related issue(s)