-
Notifications
You must be signed in to change notification settings - Fork 671
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
Add the ability of Flyteadmin to force terminate an execution #5817
Conversation
Signed-off-by: Rafael Raposo <[email protected]>
51a325a
to
b8e7b27
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5817 +/- ##
==========================================
+ Coverage 34.48% 36.35% +1.86%
==========================================
Files 1138 1304 +166
Lines 102742 110165 +7423
==========================================
+ Hits 35434 40046 +4612
- Misses 63634 65950 +2316
- Partials 3674 4169 +495
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
450c1cb
to
3821a0c
Compare
Signed-off-by: Rafael Raposo <[email protected]>
3821a0c
to
2f0262d
Compare
Signed-off-by: Rafael Raposo <[email protected]>
Signed-off-by: Rafael Raposo <[email protected]>
This was closed due to being unable to rebase and add signoffs. The replacement PR #5833 |
Tracking issue
Related to #5832
Why are the changes needed?
Add a force flag on the server side of Flyte to be able to terminate executions if FlytePropeller is not running in the kubernetes cluster.
What changes were proposed in this pull request?
This adds the force bool into
ExecutionTerminateRequest
. This in turn will be passed to thek8s_executor
. If it's a Forced termination, it will remove the finalizer from the execution CRD and delete.If it's not forced it keeps doing just a deletion (like it was before)
How was this patch tested?
Unit tested.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
TBD
Docs link
TBD