-
Notifications
You must be signed in to change notification settings - Fork 259
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
bug: S3 output configuration isn't getting passed into fluent-bit #1398
Comments
Can you check the secret created by the operator? You can get the full fluent-bit configuration file from it. |
@cw-Guo Here's the fluent-bit config secret (base64 decoded). Interestingly, it looks like the S3 output isn't getting passed in. I even tried deleting the secret and re-deploying the helm chart for the operator to see if it would re-generate properly, but no luck. Guessing something is either busted in Rancher (what I’m using to interact with the held chart via a rancher “app”) or something in the helm template is borked?
|
cc @wenchajun |
@wenchajun any insight here? Thanks! |
Describe the issue
I'm using the fluent-bit operator helm chart and I have 2 outputs enabled, elasticsearch and S3. When fluent-bit pods start (debug logging), I can see es and stderr are configured outputs, but not S3. Unfortunately, the helm chart deployments works fine and I can't find any errors related to the S3 output.
Note: I'm using Minio as a locally hosted (but outside my kubernetes cluster) S3 endpoint. I validated I can hit Minio via S3 compatible client in the same cluster and namespace
To Reproduce
Deploy fluent bit operator helm chart with ES and S3 enabled as outputs
Expected behavior
Both ES and S3 should work as outputs from fluent-bit
Your Environment
How did you install fluent operator?
Helm Chart
Additional context
This is my values.yaml configuration
Here are the logs I see on fluent-bit pod startup, indicating S3 isn't being parsed as an output, it seems
The text was updated successfully, but these errors were encountered: