-
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
Fix IsPodAvailable() to wait the PodReady is true #72
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 does not contain a valid label. Please add one of the following labels: bug, enhancement, documentation
7701682
to
559f692
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 does not contain a valid label. Please add one of the following labels: bug, enhancement, documentation
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.
559f692
to
2663570
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.
2663570
to
ad7150a
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.
ad7150a
to
5fdb190
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.
5fdb190
to
7135def
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.
This behaviour was the origin of a nasty bug with which the controller didn't respect the "MaxUnavailable" parameter. The controller was considering to many Pods as available, for example, Pods in ImagePullBackoff were considered as available.
7135def
to
e8ceb8c
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 #72 +/- ##
==========================================
+ Coverage 32.26% 32.36% +0.09%
==========================================
Files 37 41 +4
Lines 2833 2917 +84
==========================================
+ Hits 914 944 +30
- Misses 1830 1882 +52
- Partials 89 91 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This behaviour was the origin of a nasty bug with which the controller didn't respect the "MaxUnavailable" parameter. The controller was considering to many Pods as available, for example, Pods in ImagePullBackoff were considered as available.
This behaviour was the origin of a nasty bug with which the controller didn't respect the "MaxUnavailable" parameter. The controller was considering to many Pods as available, for example, Pods in ImagePullBackoff were considered as available.
What does this PR do?
Fix the function
IsPodAvailable()
used by the controller to compute the number of available Pods.Motivation
This behaviour was the origin of a nasty bug with which the controller didn't respect the "MaxUnavailable" parameter.
The controller was considering too many Pods as available, for example, Pods in ImagePullBackoff were considered as available.
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Create a EDS instance on a multi nodes cluster (you can use the kand and the
examples/kind-cluster-configuration.yaml
)when the EDS properly deployed, update it with:
The image doesn't exist. so the new pod should in
ImagePullBackoff
.wanted behaviour: Only one pod should be updated and in
ImagePullBackoff