bug: fluentbitconfig not generated for the collector stateful sets

[jnormand-gt]

Describe the issue

The collector definition points to a fluentbitconfig name. But the operator does not generator fluentbitconfig referenced by collectors, only those references by daemonsets.

To Reproduce

create a collector object and reference a valid clusterfluentbitconfig in its spec. Look at the operator logs and see nothing happening....

Expected behavior

the config and secrets should be generated for both collectors and daemonsets.

Your Environment

- Fluent Operator version: 3.2.0
- Container Runtime: GKE 1.30
- Operating system: GKE
- Kernel version: linux

How did you install fluent operator?

from the setup.yaml (removing the docker.sock, since this is not supported on gke)

Additional context

defining a daemonset works just fine and i am able to ingest logs. But i am trying to define a stateful aggregation layer with a collector object.

I think the issue is located here:

fluent-operator/controllers/fluentbitconfig_controller.go

Line 95 in cc23366

if cfg.Name != fb.Spec.FluentBitConfigName {

since there is no fluentbit object, but a collector object referencing that config

[cw-Guo]

@jnormand-gt I don't think the collector CRD works the same way with the fluentbit CRD.

you can check this line here: https://github.com/fluent/fluent-operator/blame/master/controllers/collector_controller.go#L88

@wenchajun Can you help confirm that? it looks like the collector CRD expects a secret instead of a clusterfluentbitconfig.

[saranshan2603]

Seeing the same issue, deploying a collector does not seem to do anything in the background. I don't see the stateful set nor pods getting created. Please advice on a working example of collector CRD.