-
-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconciliation reason gets stuck as "reconciler requested retry" even if short-circuited #1114
Comments
hey i'd like to take this on, if thats okay. i had a question regarding the new so
i'm open to other suggestions as well :) |
In practice this should update the reconciliation reason, fixing kube-rs#1114
In practice this should update the reconciliation reason, fixing kube-rs#1114 Signed-off-by: Natalie Klestrup Röijezon <nat@nullable.se>
* Update the scheduler message when preponing In practice this should update the reconciliation reason, fixing #1114 Signed-off-by: Natalie Klestrup Röijezon <nat@nullable.se> * Move `SingletonMessage` out of the individual tests Signed-off-by: Natalie Klestrup Röijezon <nat@nullable.se> --------- Signed-off-by: Natalie Klestrup Röijezon <nat@nullable.se>
Current and expected behavior
Currently, a reconciler that returns
Ok(controller::Action::requeue(Duration::from_secs(10)))
will always have the reconciliation reason be listed as "reconciler requested retry", even if they are triggered by an actual change. Instead, the overriding change should take priority and be listed instead.Possible solution
Currently, the controller (scheduler, actually) latches on to the first reason that it sees to schedule any given reconciliation. Instead, it should use the reason behind the earliest time to reconcile, just like how the scheduler currently allows subsequent requests to cause the reconciliation to happen earlier.
I suspect that this means that
ScheduleRequest
will need to take an extrareason
parameter, which we'd move intoScheduledEntry
.Additional context
No response
Environment
This is a kube-runtime issue, the cluster is irrelevant.
Configuration and features
Affected crates
kube-runtime
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered: