-
Notifications
You must be signed in to change notification settings - Fork 253
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
Update fluent-bit to 3.1.8 #1356
Conversation
Signed-off-by: Zoltán Reegn <[email protected]>
cede6e5
to
5f3ad90
Compare
FB_IMG ?= kubesphere/fluent-bit:v3.1.7 | ||
FB_IMG_DEBUG ?= kubesphere/fluent-bit:v3.1.7-debug | ||
FB_IMG ?= ghcr.io/fluent/fluent-operator/fluent-bit:v3.1.8 | ||
FB_IMG_DEBUG ?= ghcr.io/fluent/fluent-operator/fluent-bit:v3.1.8-debug | ||
FD_IMG ?= ghcr.io/fluent/fluent-operator/fluentd:v1.17.0 | ||
FO_IMG ?= kubesphere/fluent-operator:$(VERSION) | ||
FD_IMG_BASE ?= ghcr.io/fluent/fluent-operator/fluentd:v1.17.0-arm64-base |
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.
Is it possible to modify it here as well?
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.
You mean the kubesphere stuff? I want to handle fluent-operator in a separate PR as I'm also handling fluent-bit separately: #1357
@benjaminhuo could you also trigger a build so there's a new 3.1.8 watcher image published? |
@benjaminhuo @reegnz I'm building the v3.1.8 images now. |
v3.1.8 images have been published: https://github.com/fluent/fluent-operator/pkgs/container/fluent-operator%2Ffluent-bit |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: