-
Notifications
You must be signed in to change notification settings - Fork 138
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix bug when checking if a pod has exceeded its active deadline (#3226)
* Fix bug when checking if a pod has exceeded its active deadline The bug is that the CreationTimestamp isn't always set immediately, meaning it gets a value of 0 This in turn makes the currentRunTimeSeconds calculation massively wrong Now: - Use StartTime instead of CreationTimestamp, as kubernetes uses StartTime for its ActiveDeadline check - Return false if StartTime is not set or is 0, so we don't incorrectly calculate the run time using invalid values Signed-off-by: JamesMurkin <[email protected]> * Fix bad merge Signed-off-by: JamesMurkin <[email protected]> --------- Signed-off-by: JamesMurkin <[email protected]>
- Loading branch information
1 parent
911a7a6
commit e84e073
Showing
2 changed files
with
16 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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