-
Notifications
You must be signed in to change notification settings - Fork 479
Avoid unintentional patches to Quantity fields #7430
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
Conversation
|
|
|
Welcome @brejman! |
|
Hi @brejman. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
|
/ok-to-test |
1c9b01f to
4a217ac
Compare
|
/retest |
|
@brejman please check locally (without putting all the cases here) if this change addresses all the known problematic variants listed under the issue: #6966, in the PR: https://github.com/olekzabl/kueue/blob/38eef366ed6a3e6b64b08ab8c9800abc20d5cca3/test/integration/singlecluster/controller/admissionchecks/provisioning/provisioning_test.go#L1848-L1977 |
|
/lgtm Feel free to unhold if you confirm all cases are addressed by this change, as requested here: #7430 (comment) |
The change from no-suffix to decimal suffix doesn't seem to be detected as a diff anymore and I can't seem to reproduce the issue, even on older repo revisions, where I'm confident I was able to in the past. I'm taking a deeper look. |
|
I checked again and it does reproduce on an old revision. #7369 makes it not reproducible. Still looking into why. |
|
interesting maybe the additional layer of convertion webhooks somehow fixes the issue by additional serialization/deserialization step. If this is confirmed your PR is still worth it, bevause it will allow to fix 0.13 and 0.14. and also the issue would return when we move storage to v1beta2 and thus drop convertion webhooks again |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brejman, mimowo, olekzabl 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 |
|
/hold cancel
I patched the tests locally and changed the "stuck" expectation to "works". All test cases pass with the fix, and fail without it (checked before #7369). At HEAD the issue is not reproducible probably due to the conversion webhooks as noted previously. PTAL |
|
/lgtm |
|
@mimowo: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
LGTM label has been added. Git tree hash: 7d64e2cffab3b3e0c1538e71be9b0f270fb0b07a
|
|
@mimowo: new pull request created: #7549 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@mimowo: new pull request created: #7550 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
The cherrypicks need to be prepared "manually". The ./hack/cherry_pick_pull.sh script is useful for that |
…ty fields (#7556) * Ensure roundtrip success for Quantities * Fixed conflicts --------- Co-authored-by: Michał Woźniak <[email protected]>
…ty fields (#7557) * Ensure roundtrip success for Quantities * Fix imports * [release-0.14] Integration test for preemption from AC flavors. (#7168) * Integration test for preemption from AC flavors. * Naming fix to make a tool happy * Minor comment fix * Reduce the number of test cases * Replace testCase(...) with ginkgo.Entry(nil, ...) * Fix import ordering * Remove cases for #6966; evolve DRY -> DAMP * Forgotten: remove `admissionCheckUsage` * Adjusting to updated origin * Fixes to address comments * Forgotten: FDescribe -> Describe * Forgotten follow-up --------- Co-authored-by: Olek Zabłocki <[email protected]> --------- Co-authored-by: Michał Woźniak <[email protected]> Co-authored-by: Olek Zabłocki <[email protected]>
What type of PR is this?
/kind bug
What this PR does / why we need it:
In case the job requests memory in decimal format (e.g. "1G"), the Workload's
status.admission.podSetAssignments[].resourceUsage.memoryis unintentionally patched due to Quantity round trip issues.For example:
This PR changes no.3 to auto-detect the format and avoid unintentional diff.
While normally such diff shouldn't really matter other than adding some noise in managed fields, it hits kubernetes/kubernetes#134902, which makes the workload impossible to evict.
Which issue(s) this PR fixes:
Fixes #6966
Special notes for your reviewer:
This change makes it much more expensive to compute the Quantity.
I've considered a couple of alternatives:
Does this PR introduce a user-facing change?