bug: With stakater reloader restart option, one replica is getting restarted

[btalakola]

Describe the issue

Hi @cw-Guo & Team, 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 is restarting only one replica of fluent-bit daemonset though the "kubectl rollout restart daemonsets fluent-bit -n namespace-dummy" 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!

Similar issue ref : https://github.com/fluent/fluent-operator/issues/1479

To Reproduce

Deployed fluent-bit using fluent-operator with v3.3.0. I am using stakater reloader to restart the fluent-bit pods in case of any configurational changes. This actually restarting only one replica of fluent-bit daemonset

Expected behavior

With stakater reload option, should actually restart all the replicas.

Your Environment

- Fluent Operator version:v3.3.0
- Container Runtime:
- Operating system:
- Kernel version:

How did you install fluent operator?

No response

Additional context

No response