-
Notifications
You must be signed in to change notification settings - Fork 351
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
[jaeger] fixes #329 missing prefix on esCronJobs #414
[jaeger] fixes #329 missing prefix on esCronJobs #414
Conversation
Hi @mehta-ankit, |
2c7c795
to
d43c172
Compare
Hi anybody to check this PR, please? |
looking into 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.
LGTM
@Mouness can you maybe please squash commits into 1 commit and gpg sign the commit (currently you have 3 commits and 2 are not gpg signed). Thanks |
3d350a9
to
bc082c2
Compare
Hi @mehta-ankit , |
Signed-off-by: Mounir <mounir.arrahmani@outlook.com>
bc082c2
to
2ec9b7f
Compare
Sorry for the back and forth I had to setup gpg locally |
no problem. Thanks a lot for squashing them 😄 (i appreciate it) |
@@ -34,7 +34,7 @@ dependencies: | |||
repository: https://helm.elastic.co | |||
condition: provisionDataStore.elasticsearch | |||
- name: kafka | |||
version: ^19.1.5 | |||
version: ^18.0.8 |
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.
Why was this reverted to 18.x?
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.
@gburton1 If i have to guess it would have been an oversight and not an intentional change. Maybe during squashing of the commits/resolving conflicts in this MR, this change got in.
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.
Hi @gburton1, it was not intentional. It probably happened during the squash. Do you want to create a new PR to revert this change?
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.
What this PR does
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format,will close that issue when PR gets merged)
Checklist
[jaeger]
or[jaeger-operator]
)