bug: Restarting the fluentbit daemonset is not restarting all the fluentbit replicas. It is just restarting only one replica

[btalakola]

Describe the issue

HI Team, I restarted fluentbit daemonset using "kubectl rollout restart daemonsets fluent-bit -n ". But it is just restarting only one replica and not restarting all the replicas. I am using stakater reloader if there are any configurational changes as hot reload/fluent-watcer is not working very effectively Please suggest how to resolve it.

To Reproduce

• Fluent Operator version:
• Container Runtime:
• Operating system:
• Kernel version:

Expected behavior

Restarting daemonset should restart all the replicas instead just one.

Your Environment

- Fluent Operator version:
- Container Runtime:
- Operating system:
- Kernel version:

How did you install fluent operator?

No response

Additional context

No response

[cw-Guo]

this has been fixed but not released yet. we will try to release a newer version soon.

See #1375.

[btalakola]

Sure Thank you @cw-Guo. Could you please provide the tentative date as we have some dependency on this?

[btalakola]

HI Team, I can see 3.3.0 version in charts. But I didn't find any release with 3.3.0 for fluent operator.

[cw-Guo]

@btalakola the release is still in progressing. a few PRs is still in review.

[btalakola]

Hi @cw-Guo, Deployed fluent-bit using fluent-operator with v3.3.0. I am using stakater reloader as below to restart the fluent-bit pods in case of any configurational changes:

Restart fluent-bit daemonset using stakater relaoder if there are any configurational changes.

fluent-bit
annotations:
secret.reloader.stakater.com/reload: "fluent-bit-config"

This actually restarting only one replica of fluent-bit daemonset though the "kubectl rollout restart daemonsets fluent-bit -n " restarting all the replicas. Is there anything that I need to work on using stakater reloader? Can you please please help me out here. Thanks in advance!