from here I can rework the controller-runtime upgrade and will this time also see if I can then add some e2e test to cover the problem introduced earlier.

@Marco Franssen @Chengwei Guo Can the three of us get together and figure out exactly what we need to get Renovate up and working? I don't think we need to install the Renovate application since we're running Renovate self-hosted in CI. I think we just need credentials. Sound right?

I opened 2 small PRs to cleanup dependabot

is it ok to merge https://github.com/fluent/fluent-operator/pull/1585?

Another small PR to ensure helm tests are executed when changes to the chart happen https://github.com/fluent/fluent-operator/pull/1597

@Josh Baird @Chengwei Guo could anyone of you review my PRs? https://github.com/fluent/fluent-operator/pull/1594 https://github.com/fluent/fluent-operator/pull/1595

What would be required to cut a new release?

https://github.com/fluent/fluent-operator/pull/1605 small PR to fixup the crds (descriptions only)

https://github.com/fluent/helm-charts/pull/602/files prepared the release for the helm-chart. On the operator repo all PRs are merged. @Benjamin Huo @Chengwei Guo could you have a look to get the release out?

@Marco Franssen I think we need to attach the

setup.yaml

to the release.

@Chengwei Guo @Benjamin Huo @Wanjun Lei @Josh Baird what is required to get the helm-chart PR merged? https://github.com/fluent/helm-charts/pull/602/files

Hi! can i get help here with clusterfilters / clusterparsers?

https://github.com/fluent/helm-charts/pull/603/files small PR ready for review

I wonder if we don't need a maintainer+community meeting to talk about our release process. It could use some attention. 🙂

Hi there We are using fluent-operator and the ClusterOutput CRD to define the Splunk Output Plugin. Is there a way to dynamically set eventIndex, eventSource and eventSourcetype (except using os env)?

https://github.com/fluent/fluent-operator/pull/1623 think this is what is required to patch up the entire chart release

Hey @Marco Franssen @Josh Baird, you should now both have access to fluent helm charts repository

@Marco Franssen @Chengwei Guo re: the Helm chart.. do you find it confusing that we maintain a "local" copy of the chart in the fluent-operator repo and then have to manually sync to helm-charts to release?

Hi team! When I tried to run ghcr.io/fluent/fluent-bit:4.0.3 I run into trouble not having any of my config actually properly propagated despite the fact that I can observe it being mounted. Afterwards, I switched to ghcr.io/fluent/fluent-bit:4.0.3-debug where I can see entrypoint being

root           1  0.0  0.0  85760 14480 ?        Ssl  10:08   0:00 /fluent-bit/bin/fluent-bit -c /fluent-bit/etc/fluent-bit.conf

Whereas my config is landed at

/fluent-bit/config

Is it a bug of 3.4.0 version of an operator, or intended, or there's some other thing I have completely forgotten to configure by any chance?

Not sure if this is the correct channel. I am using the fluent-operator and I am running into an issue where sometimes when fluent-bit pods startup they are unable to send data to the backend. It never sends logs and then if I restart the pod everything seems to start working. I am running as a daemonset. I am sending metrics via opentelemetry and logs via forward. • How I can get more information about why the failure is happening? • Any strategies I can employ to recover or fix this? A sample of the logs I see looks like the following

[2025/07/01 16:39:09] [error] [io fd=123] error sending data to: <tcp://10.0.75.209:24224> (Broken pipe)
[2025/07/01 16:39:09] [error] [output:forward:forward.0] could not write forward entries
[2025/07/01 16:39:09] [ warn] [engine] failed to flush chunk '14-1751387948.402920859.flb', retry in 11 seconds: task_id=0, input=tail.1 > output=forward.0 (out_id=0)
[2025/07/01 16:39:20] [error] [io fd=123] error sending data to: <tcp://10.0.75.209:24224> (Broken pipe)
[2025/07/01 16:39:20] [error] [output:forward:forward.0] could not write forward entries
[2025/07/01 16:39:20] [error] [engine] chunk '14-1751387948.402920859.flb' cannot be retried: task_id=0, input=tail.1 > output=forward.0
[2025/07/01 16:39:49] [error] [http_client] broken connection to redacted.svc.cluster.local:4318 ?
[2025/07/01 16:39:49] [error] [output:opentelemetry:opentelemetry.1] redacted.svc.cluster.local:4318, HTTP status=0
[2025/07/01 16:39:49] [ warn] [engine] failed to flush chunk '14-1751387988.401066631.flb', retry in 6 seconds: task_id=0, input=fluentbit_metrics.0 > output=opentelemetry.1 (out_id=1)

Hi team! I got curious if there's somewhere by any chance community library of solutions built on top of fluent-operator. If there're any other resources aside of https://doc.crds.dev/github.com/fluent/fluent-operator/fluentbit.fluent.io/ClusterFilter/v1alpha2@v3.4.0 it would be great to know (amazing documentation formatting for the CRDS btw)

Hi team, I'm running Fluent Bit via the Fluent Operator and using a Lua filter to drop logs based on log level. Here's a snippet of my filter config:

- lua:
    call: normalize_product_logs
    script:
      name: fluent-bit-modify-k8s-fields
      key: custom.lua

The

custom.lua

script uses environment variables like

drop_error_product

,

drop_debug_product

, etc., to control which logs should be dropped dynamically. For example:

if log_level == "ERROR" and drop_error_product == "true" then
  return -1  -- drop log
end

These variables are passed via environment variables in the Fluent Bit container or set via config maps. Problem When I update the values of these variables (e.g., setting

drop_error_product

from

false

to

true

) and confirm that the

ConfigMap

is updated and pods are restarted manually, the updated logic does not take effect. However, the moment I: • remove the entire Lua block from the filter config and deploy • then add the same Lua block back and deploy again ...the changes start reflecting and logs get dropped correctly. Is Fluent Bit or the Lua plugin caching the script or its environment somewhere internally? Is there a supported or recommended way to force Fluent Bit to reload updated Lua script logic and/or environment config? Thanks a lot — any insights or best practices would be appreciated!

Is there planned support for processor plugins for fluent bit?

FYI: https://github.com/fluent/fluent-operator/issues/1657

If we were to organize a fluent-operator community meeting to discuss release strategy, etc -- what time would be best for everyone? I know we have interested folks and maintainers in a variety of different time zones.

I’m out for 3 weeks camping ⛺ end of this week

I'd say maybe get @Eric D. Schabell / @eduardo to ask as well in the existing Fluent office hours/community meeting so more folks are aware

Hi! Not sure if this is the right channel, but could someone help review this PR for the Fluent Operator Helm chart? It’s a small change that just adds extra labels to the Operator’s Deployment. I’m not the author, but I’m also waiting on it. https://github.com/fluent/helm-charts/pull/623