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: Fluentd configuration file is different for each reconciliation, even if no modification is done #1104

Closed
antrema opened this issue Apr 3, 2024 · 2 comments · Fixed by #1106

Comments

@antrema
Copy link
Collaborator

antrema commented Apr 3, 2024

Describe the issue

Create thousands of filter.fluentd.fluent.io and fluentdConfig.fluentd.fluent.io in the cluster.
Compare the configuration file each time it reconcile, it is different.
An infinite reconciliation loop is launched and Fluentd pods are infinitely reloading configuration.

To Reproduce

Create thousands of filter.fluentd.fluent.io and fluentdConfig.fluentd.fluent.io in the cluster.
Compare the configuration file each time it reconcile, it is different

Expected behavior

The generated configuration file is the same each time it reconcile (when no modification is done)

Your Environment

- Fluent Operator version: kubesphere/fluent-operator:v2.7.0
- Container Runtime: containerd://1.6.15
- Operating system: Ubuntu 22.04.1 LTS
- Kernel version: 5.15.0-46-generic

How did you install fluent operator?

kubectl create ns fluent 
kubectl apply -f https://raw.githubusercontent.com/fluent/fluent-operator/release-2.0/manifests/setup/setup.yaml

Additional context

Proposed solution: create an ordered configuration file based on @id, name and tag

@antrema
Copy link
Collaborator Author

antrema commented Apr 3, 2024

I will propose a PR to correct this behaviour

@benjaminhuo
Copy link
Member

I will propose a PR to correct this behaviour

That's great!

antrema added a commit to antrema/fluent-operator that referenced this issue Apr 4, 2024
Signed-off-by: Anthony TREUILLIER <[email protected]>
benjaminhuo added a commit that referenced this issue Apr 4, 2024
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

Successfully merging a pull request may close this issue.

2 participants