[sig-scheduling] Exception request for KEP-5229 Implementation

[Maciej Skoczeń]

- Enhancement name:
  - Asynchronous API calls during scheduling
- Enhancement status (alpha/beta/stable):
  - beta
- SIG:
  - Scheduling
- k/enhancements repo issue #:
  - https://github.com/kubernetes/enhancements/issues/5229
- PR #’s:
  - https://github.com/kubernetes/kubernetes/pull/132886
  - https://github.com/kubernetes/kubernetes/pull/133120 (could be merged into the first PR)
- Additional time needed (in days):
  - 5 (until Tuesday)
- Reason this enhancement is critical for this milestone:
  - This KEP clearly improves kube-scheduler's performance when processing unschedulable pods. Future enhancements to kube-scheduler (1.35+) plan to rely on this mechanism to not block the scheduler when sending new API calls.
- Risks from adding code late: (to k8s stability, testing, etc.)
  - This enhancement is guarded by the feature gate and modifies only one component (kube-scheduler). Kube-scheduler is well covered by tests, and PR keeps that coverage for the enhancement, so the risk is considered low.
- Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
  - Unschedulable pods processing will still rely on a blocking API call, reducing the performance visibly in large clusters.

 The delay was caused by limited availability of SIG Scheduling approvers in this release cycle.

Thanks for your consideration,
Maciej

[Dominik Marciński]

+1

--
You received this message because you are subscribed to the Google Groups "sig-scheduling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-schedulin...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-scheduling/CAPpz9YtL0ccW1KjEYM3KS_P1Dsz%3DSBc9mgRSf83q7eCuz9g9uQ%40mail.gmail.com.