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
The claim scheduling and defaulting reconcilers currently return reconcile.Result{Requeue: false} if they find no suitable resource classes. This means that if they don't find a suitable resource class for a newly submitted claim they'll never reprocess it, even if a suitable resource class appears later.
How could Crossplane help solve your problem?
The defaulting and scheduling reconcilers could return reconcile.Result{RequeueAfter: aShortWait} if they found no resource classes - this means they'd try again to default or schedule the resource claim after a short wait, in case a suitable class was created. If another controller found and set a suitable class the queued reconcile would be dropped by our controller predicates, which filter out any resource claims with a classRef set.
The text was updated successfully, but these errors were encountered:
What problem are you facing?
The claim scheduling and defaulting reconcilers currently return
reconcile.Result{Requeue: false}
if they find no suitable resource classes. This means that if they don't find a suitable resource class for a newly submitted claim they'll never reprocess it, even if a suitable resource class appears later.How could Crossplane help solve your problem?
The defaulting and scheduling reconcilers could return
reconcile.Result{RequeueAfter: aShortWait}
if they found no resource classes - this means they'd try again to default or schedule the resource claim after a short wait, in case a suitable class was created. If another controller found and set a suitable class the queued reconcile would be dropped by our controller predicates, which filter out any resource claims with aclassRef
set.The text was updated successfully, but these errors were encountered: