-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Solidify UnavailableReplicas field for Deployments #41789
Comments
Punting for 1.7 but I think this is just a api doc change. UnavailableReplicas is fine for meaning the unavailable replicas that either werent created or are simply not available yet, we just need to make this clearer in the api comment. |
/cc |
Punting for 1.8 |
I am volunteered to take this if nobody start working on this |
@wanghaoran1988 this is only a doc update - I am going to update the API comments during the 1.8 timeframe. |
@Kargakis Cool, thanks for clarification. |
/kind cleanup |
[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings:
Additional instructions available here
|
Automatic merge from submit-queue (batch tested with PRs 51590, 48217, 51209, 51575, 48627) api: clarify d.status.unavailableReplicas Fixes #41789 @kubernetes/sig-apps-api-reviews
kubernetes/pkg/apis/extensions/types.go
Lines 323 to 325 in 1cb737f
This is assuming we count unavailable pods from all created pods targeted by a Deployment.
In the controller, we calculate unavailable replicas based on spec.replicas which also includes pods that haven't been created.
kubernetes/pkg/controller/deployment/sync.go
Lines 594 to 595 in 1cb737f
We either need to fix the controller to use status.replicas instead of spec.replicas and in both cases update the godoc to explain better the intent of the field.
@kubernetes/sig-apps-api-reviews
The text was updated successfully, but these errors were encountered: