Skip to content

Ensure to have always only one retry or re-schedule event in place for a CustomResource #61

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

Closed
snowdrop-bot opened this issue Oct 13, 2021 · 0 comments

Comments

@snowdrop-bot
Copy link

Currently it can happen that there are multiple events scheduled from reSchedule funtionality. This should not happen, there should be at most one, possibly the earliest keeped in such case. In addition to that we have a automated retry functionality, so we have to think about how this two should work together.

Ideally there is always only 1 of these to is scheduled types scheduled. But also in general there should be at most one timed event coming either of these functionalities.


operator-framework#601


$upstream:601$

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants