Skip to content
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: fluentbitconfig not generated for the collector stateful sets #1436

Open
jnormand-gt opened this issue Dec 11, 2024 · 1 comment
Open

Comments

@jnormand-gt
Copy link

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:

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

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

@cw-Guo
Copy link
Collaborator

cw-Guo commented Dec 14, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants