Monitor deployed tasks and update status in case of crashes #404
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed or are not found in the cluster anymore.
118fe96 to
cb54ec6
Compare
lkurija1
approved these changes
May 4, 2023
dhruvsgarg
pushed a commit
to dhruvsgarg/flame
that referenced
this pull request
Oct 18, 2024
…ed or are not found in the cluster anymore. (cisco-open#404)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When we deploy tasks thru deployer, we don't actually monitor if the given created pod crashes after it has been created.
To solve this we now retrieve the running jobs from controller to deployer service, and also the tasks associated with those jobs in order to check if there are still tasks which haven't received the fail status. In case the pod crashed then we update the status for that particular task and also for the job.
Type of Change
Checklist