Introduce new image v1.16-4.8 for next version with updated label router #134
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
pepov
force-pushed
the
label-router-update
branch
4 times, most recently
from
f17ddf3
to
9ebec0c
Compare
pepov
changed the title
Signed-off-by: Peter Wilcsinszky <[email protected]>
Signed-off-by: Peter Wilcsinszky <[email protected]>
Signed-off-by: Peter Wilcsinszky <[email protected]>
pepov
force-pushed
the
label-router-update
branch
from
7622fe1
to
60f721a
Compare
pepov
changed the title
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.
Introduce new image
v1.16-4.8that will be used with the next logging operator version4.8(hence the suffix). Also do not buildv1.16-ruby3.3anymore as it was not used and broken.Update sumo base image and some upstream deps to avoid multiple versions from the same gem.
The new image contains an update for the label router to support namespace label based routing, see: kube-logging/fluent-plugin-label-router#21