feat(fluent-bit): Updated image to 3.2.1 #571
Merged
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: Steve Hipwell <[email protected]>
patrick-stephens
approved these changes
Nov 20, 2024
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.
This PR updates the Fluent Bit version to 3.2.1. It also reverts the change to image pull policy made in #565 which serves no purpose, besides inflating the Docker pulls, given the image reference is immutable; the major downside of this is that it can cause Docker Hub rate limits to quickly be hit as every time a container starts on a node the image index will be pulled even if the image already exists. For reference the reason the chart originally had a pull policy of
Alwayswas that it used a mutable tag (such asv2) that was allowed to update on each container start.CC @patrick-stephens