Skip to content
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

Claim defaulting and scheduling reconcilers should requeue #57

Closed
negz opened this issue Oct 25, 2019 · 0 comments · Fixed by #71
Closed

Claim defaulting and scheduling reconcilers should requeue #57

negz opened this issue Oct 25, 2019 · 0 comments · Fixed by #71
Assignees
Labels
enhancement New feature or request

Comments

@negz
Copy link
Member

negz commented Oct 25, 2019

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 a classRef set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant