-
Notifications
You must be signed in to change notification settings - Fork 450
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 collector config update #670
Conversation
|
ed44dcb
to
2b4da33
Compare
|
@pavolloffay Can you review it? |
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.
Thanks for looking into this and it looks good to me ❤️
I would love to see e2e test for this change (something like this)
- deploy collector as deployment
- assert it is deployed
- change config in CR - e.g. add new receiver
- assert the collector pod restarted with the new changes - check if the new receiver port is exposed.
|
Done, please review it. |
8a1bb8b
to
68e98df
Compare
|
557ed9d
to
f216c31
Compare
|
1b175bd
to
f216c31
Compare
@pavolloffay @Aneurysm9 Can we merge it before the next release? |
yes, thanks for the PR :) cc) @jpkrohling @VineethReddy02 could you please merge? |
* fix/460 : Added opentelemetry-operator-config/sha256 annotaton to pod annotations * PR comments fixes * Created e2e test
I added check sum to pod annotations. This will fix rollout when the collector config changes.
Yes, I know this is duplicated pull request with #506
but the other one has been forgotten for some time.
Fixes #460