You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HI Team,
Deployed fluent-bit using fluent-operator. But if there are any configurational changes, just fluent-bit-config secret is getting updated but those changes are not effective unless we manually restarted fluent-bit pods. Tried adding hotReload flag in ClusterFluentBit customresource. It is not working.
Can you please help us how to enable/configure fluent-watcher for fluent-bit?
Also one more concern, if we restart the fluent-bit daemonset using "kubectl rollout restart daemonsets fluent-bit -n , it is not actually restarting all the replicas. It is just restarting only one replica. Can you please confirm is this expected behaviour?
How did you install fluent operator?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I deployed fluent-bit using fluent-operator with latest version v3.2.0. It internally used fluent-bit version 3.1.7
image:
repository: "ghcr.io/fluent/fluent-operator/fluent-bit"
tag: "3.1.7"
Describe the issue
HI Team,
Deployed fluent-bit using fluent-operator. But if there are any configurational changes, just fluent-bit-config secret is getting updated but those changes are not effective unless we manually restarted fluent-bit pods. Tried adding hotReload flag in ClusterFluentBit customresource. It is not working.
Can you please help us how to enable/configure fluent-watcher for fluent-bit?
Also one more concern, if we restart the fluent-bit daemonset using "kubectl rollout restart daemonsets fluent-bit -n , it is not actually restarting all the replicas. It is just restarting only one replica. Can you please confirm is this expected behaviour?
How did you install fluent operator?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: