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,
We are facing the following behaviour of the operator:
Once in a while, the operator decides to reconcile all objects that can be seen from queue depth of each controller:
This seems weird because we don't use time based reconciliation and we don't run a mass update of all RMQ objects in our cluster.
I am reporting this here as I am not sure if it's a bug or not.
The Operator does not reconcile an object unless there's an event for said object. It watches for updates/deletes of any kind i.e. updates to the spec and/or the metadata. The other situation where all objects are reconciled is after the Operator restarts.
Hi,
We are facing the following behaviour of the operator:
Once in a while, the operator decides to reconcile all objects that can be seen from queue depth of each controller:
This seems weird because we don't use time based reconciliation and we don't run a mass update of all RMQ objects in our cluster.
I am reporting this here as I am not sure if it's a bug or not.
Operator version: 1.12.0
EKS version: v1.25.16-eks-db838b0
The text was updated successfully, but these errors were encountered: