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
we observed an interesting behavior that after an status update without any change leads to an reschedule of the resource, which triggers the reconcile loop again.
2024-05-15T15:18:43+02:00 INFO Reconcile .... {"controller": "stream", "reconcileID": "fad5bca2-9729-4799-b05c-80a2e9d929a8"}
2024-05-15T15:18:43+02:00 INFO Reconcile .... {"controller": "stream", "reconcileID": "521a821c-49fb-42fc-a07e-78f977a6f109"}
Why does it not trigger more than two times after object creation? If an update on the status leads to a new reconciling, we would expect an infinite loop without sleeping/delay.
How could we ensure that the object is just once reconciled?
Used controller-runtime version:
sigs.k8s.io/controller-runtime v0.16.3
Thx, Regards
The text was updated successfully, but these errors were encountered:
After some investigation it seems that the resource version does not change after the second reconciliation. which then stops to send updates to the controller. Detection of Resource Changes
Hi all,
we observed an interesting behavior that after an status update without any change leads to an reschedule of the resource, which triggers the reconcile loop again.
Code that is executed in the reconcile loop:
Output after the resoruce creation:
2024-05-15T15:18:43+02:00 INFO Reconcile .... {"controller": "stream", "reconcileID": "fad5bca2-9729-4799-b05c-80a2e9d929a8"}
2024-05-15T15:18:43+02:00 INFO Reconcile .... {"controller": "stream", "reconcileID": "521a821c-49fb-42fc-a07e-78f977a6f109"}
Why does it not trigger more than two times after object creation? If an update on the status leads to a new reconciling, we would expect an infinite loop without sleeping/delay.
How could we ensure that the object is just once reconciled?
Used controller-runtime version:
sigs.k8s.io/controller-runtime v0.16.3
Thx, Regards
The text was updated successfully, but these errors were encountered: