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
Every time any fluentdConfig CRD is changed, the reloader runs a complete control loop and re-checks all fluentdConfigs in all namespaces, which takes a very long time in our clusters with 100s/1000s of configs applied. Is it possible to limit the check to only the fluentdConfig that changed?
The text was updated successfully, but these errors were encountered:
Reported by @alex-vmw:
Every time any fluentdConfig CRD is changed, the reloader runs a complete control loop and re-checks all fluentdConfigs in all namespaces, which takes a very long time in our clusters with 100s/1000s of configs applied. Is it possible to limit the check to only the fluentdConfig that changed?
The text was updated successfully, but these errors were encountered: