koord-scheduler: support select reservation via reservation affinity

[eahydra]

Ⅰ. Describe what this PR does

If a pod has an affinity annotation, the pod must be allocated from the reservation, otherwise it stops scheduling.

Ⅱ. Does this pull request fix one issue?

fix #1087 #1256

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests
• All checks passed in make test

[eahydra]

/hold

[codecov]

Codecov Report

Patch coverage: 38.66% and project coverage change: -0.08 ⚠️

Comparison is base (d9985ea) 65.08% compared to head (11317c8) 65.01%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1265      +/-   ##
==========================================
- Coverage   65.08%   65.01%   -0.08%     
==========================================
  Files         309      309              
  Lines       32520    32589      +69     
==========================================
+ Hits        21167    21188      +21     
- Misses       9813     9858      +45     
- Partials     1540     1543       +3     

Flag	Coverage Δ
unittests	65.01% <38.66%> (-0.08%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/scheduler/frameworkext/interface.go	83.33% <ø> (ø)
pkg/util/reservation/reservation.go	40.76% <0.00%> (-5.52%)	⬇️
pkg/scheduler/frameworkext/framework_extender.go	74.53% <20.00%> (-1.41%)	⬇️
pkg/scheduler/plugins/reservation/plugin.go	85.30% <62.50%> (+0.49%)	⬆️
pkg/scheduler/plugins/reservation/transformer.go	65.06% <74.19%> (+1.38%)	⬆️

... and 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[hormes]

When the Pod declares the annotation, does the selection condition of the Reservation for the Pod still take effect?

[eahydra]

Yes, still take effect. Reservation.Spec.Owners is currently required. If we abandon this required condition, even if the Pod declares the Reservation Affinity Annotation, some strange usages will appear. For example, it is possible that a Reservation can be freely used by Pods other than the target.

[eahydra]

/hold cancel
TBR. PTAL @hormes @FillZpp

[FillZpp]

/lgtm

[FillZpp]

/lgtm

[FillZpp]

/lgtm

[koordinator-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FillZpp, hormes

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [hormes]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment