Open sdwerwed opened 1 year ago
Hi, I assume the secret you are referring to is this: fluentd-opensearch
. In this case, you either have to run the reloader in the same namespace or run it in cluster scope by setting the watchGlobally
flag to true.
@faizanahmad055 It is globally already, reloader.watchGlobally: true
in the default values.yaml
Looks like the issue is on the way the secret is changing, if I run kubectl edit secret fluentd-opensearch
reloader works as expected. If the secret is getting deleted and gets applied with new values it is not detecting the changes.
In that case, you need to set the reloadOnCreate flag.
In that case, you need to set the reloadOnCreate flag.
That works thnx! I think would be nice to set true as the default to avoid such confusion. Many sync controllers might delete and apply instead of edit in place.
@sdwerwed can this be closed?
@sdwerwed can this be closed?
I would recommend to make the default reloadOnCreate flag true, to avoid such kind confusion unless there is a reason to keep it as it is.
metadata.annotations: reloader.stakater.com/auto: "true"
is not working, no information why rollout restart not starting. I followed the README info how to set the annotation and looks like it is not working as described. I use the latest reloader helm chartv1.0.22
with default values https://artifacthub.io/packages/helm/stakater/reloader/1.0.22 Statefulset and reloader are in different namespacesLogs of reloader-reloader:
Statefulset manifest