-
Notifications
You must be signed in to change notification settings - Fork 13
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
[eds] Introduce PodCannotStart condition and canary auto-pause handling #68
[eds] Introduce PodCannotStart condition and canary auto-pause handling #68
Conversation
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
a72d934
to
ae09707
Compare
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.
This pull request contains a valid label.
Codecov Report
@@ Coverage Diff @@
## master #68 +/- ##
==========================================
+ Coverage 31.39% 31.68% +0.28%
==========================================
Files 37 37
Lines 2758 2818 +60
==========================================
+ Hits 866 893 +27
- Misses 1809 1839 +30
- Partials 83 86 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
- Introduces logic to handle certain failure waiting states as cause for auto-pausing canary. - Simplifies logic for reported container states in terminated reason (will basically take anything). - e2e tests for PodCannotStart scenarios (container config error and image pull errors).
ae09707
to
466aaa9
Compare
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
- Improve logging - Colorize e2e test milestone logs - Add error logs around reconciler scenarios on update, still require more investigation.
635da0e
to
3405370
Compare
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.
This pull request contains a valid label.
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.
This pull request contains a valid label.
What does this PR do?
PodCannotStart
conditions/scenarios (container config error and image pull errors).Motivation
Current limitations in support for container waiting state which are abnormal and should result in pausing canary.
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Scenarios similar to tests in e2e.