-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
chore: Don't degrade PDB on InsufficientPods (#20171) #20665
chore: Don't degrade PDB on InsufficientPods (#20171) #20665
Conversation
❌ Preview Environment deleted from BunnyshellAvailable commands (reply to this comment):
|
0cff32a
to
5b76ced
Compare
Closes argoproj#20171 There are valid use cases for InsufficientPods, e.g. running some jobs or tests that don't want to be terminated. See the discussion on the issue for more details. So don't degrade the PDB on InsufficientPods condition. This needs to be cherry picked to 2.13, as many people may not upgrade otherwise. Signed-off-by: Andrii Korotkov <[email protected]>
5b76ced
to
8f645d3
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #20665 +/- ##
=========================================
Coverage ? 55.09%
=========================================
Files ? 324
Lines ? 55239
Branches ? 0
=========================================
Hits ? 30433
Misses ? 22190
Partials ? 2616 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also a user of PDBs and wouldn't want our apps to be in the degraded state during "normal" operations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Looks like health check was introduced in 2.13 and it might be a bit aggressive. This PR is making it less aggressive so change makes sense to me.
/cherry-pick release-2.13 |
Closes #20171 There are valid use cases for InsufficientPods, e.g. running some jobs or tests that don't want to be terminated. See the discussion on the issue for more details. So don't degrade the PDB on InsufficientPods condition. This needs to be cherry picked to 2.13, as many people may not upgrade otherwise. Signed-off-by: Andrii Korotkov <[email protected]>
Closes #20171 There are valid use cases for InsufficientPods, e.g. running some jobs or tests that don't want to be terminated. See the discussion on the issue for more details. So don't degrade the PDB on InsufficientPods condition. This needs to be cherry picked to 2.13, as many people may not upgrade otherwise. Signed-off-by: Andrii Korotkov <[email protected]> Co-authored-by: Andrii Korotkov <[email protected]>
Closes #20171
There are valid use cases for InsufficientPods, e.g. running some jobs or tests that don't want to be terminated. See the discussion on the issue for more details. So don't degrade the PDB on InsufficientPods condition.
This needs to be cherry picked to 2.13, as many people may not upgrade otherwise.
Checklist: