Bump Jaeger to 1.13 #504
Merged
Bump Jaeger to 1.13 #504
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
|
cc @kevinearls |
objectiser
approved these changes
Jul 4, 2019
|
I would prefer to have it done before we reach the release phase, as version changes in Jaeger typically come with new options that we'll need to support in the operator. |
|
That said, the release script could indeed check this and block the release if there's a mismatch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I apparently released the Operator 1.13 while we were still pointing the default underlying image to 1.12. This PR fixes that, making 1.13 the default version for the Operator 1.13.1.
Signed-off-by: Juraci Paixão Kröhling [email protected]