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
Track ready pods in Job status #104915
Track ready pods in Job status #104915
Conversation
2294ce2
to
baef607
Compare
Consensus that this is mostly sig apps |
baef607
to
b2506cf
Compare
/assign @soltysh |
/label api-review /remove-sig api-machinery |
ed49297
to
5009d64
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.
Also added validation for non-negative ready field.
5009d64
to
1496d65
Compare
/retest |
|
1496d65
to
e51f320
Compare
api changes lgtm (after controller changes need lgtm from apps approver |
e51f320
to
b0d388f
Compare
Removed the roundtrip file |
API changes lgtm |
/retest |
1 similar comment
/retest |
to keep a count of the pods that have the ready condition. Also: - Add feature gate JobReadyPods. - Add Ready to describe. Change-Id: Ib934730a430a8e2a2f485671e345fe2330006939
When the feature gate JobReadyPods is enabled. Change-Id: I86f93914568de6a7029f9ae92ee7b749686fbf97
Change-Id: I1f20657f4f9cd4daad73149f969bad52a33698fa
b0d388f
to
68f2c89
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.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, liggitt, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/kind api-change
/sig apps
What this PR does / why we need it:
Add field .status.ready to track the number of ready pods in a Job.
The feature is guarded by feature gate JobReadyPods. To reduce the number of Job status updates that this new tracking might cause, Pod updates are batched in intervals of 0.5s.
Which issue(s) this PR fixes:
Ref kubernetes/enhancements#2879
Special notes for your reviewer:
First commit has the API changes.
I couldn't find a significant difference in the runtime of the integration tests between different batch periods. I'm leaving this at 0.5s to be conservative. We can reconsider when going to beta.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: