This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
Adding a
cleanupOnFailure
field to thePhaseInfo
reported by each task evaluation. This is useful to track situations where Flyte marks a task asFAILED
but it should still be cleaned up during the workflow abort. An example isImagePullBackoff
where a k8sPod
requests an image that does not exist. Flyte will mark thePod
as a failure, but it is not cleaned up until the workflow CR is garbage collected. ThePod
will continually reattempt to download the missing image (with backoff) maintaining it's hold on resources.Type
Are all requirements met?
Complete description
^^^
Tracking Issue
flyteorg/flyte#3239
Follow-up issue
NA