-
Notifications
You must be signed in to change notification settings - Fork 219
Make it possible to configure graceful shutdown of controllers execution threads #421
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
Comments
metacosm
added a commit
that referenced
this issue
May 20, 2021
metacosm
added a commit
that referenced
this issue
May 20, 2021
metacosm
added a commit
that referenced
this issue
May 21, 2021
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Jun 1, 2021
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Jun 1, 2021
metacosm
added a commit
to quarkiverse/quarkus-operator-sdk
that referenced
this issue
Jun 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Controllers launch threads to execute their tasks. When the operator is shut down, we should be able to configure how these threaded tasks get resolved; in particular, how long, if at all, do we need to wait for these threads to finish executing their tasks before the operator is actually shut down.
The text was updated successfully, but these errors were encountered: