Re: [sig-scheduling] Exception request for KEP-5278 Implementation

[Dominik Marciński]

+1

On Fri, Jul 25, 2025 at 12:38 PM 'Maciej Skoczeń' via sig-scheduling <sig-sch...@kubernetes.io> wrote:

+1

On Fri, Jul 25, 2025 at 12:34 PM Kensei Nakada <handb...@gmail.com> wrote:

Hi team,

I'm requesting the exception request for KEP-5278. 

The delay was caused by the unexpected bandwidth limitation of SIG-Scheduling leads.

- Enhancement name:
  - Use NominatedNodeName to express the expected pod placement
- Enhancement status (alpha/beta/stable):
  - beta
- SIG:
  - Scheduling
- k/enhancements repo issue #:
  - https://github.com/kubernetes/enhancements/issues/5278
- PR #’s:

- https://github.com/kubernetes/kubernetes/pull/132439
- https://github.com/kubernetes/kubernetes/pull/132443
- https://github.com/kubernetes/kubernetes/pull/133021
- https://github.com/kubernetes/kubernetes/pull/133213

- Additional time needed (in days):
  - 5
- Reason this enhancement is critical for this milestone:

  - This KEP is the first step for workload-aware scheduling. If we couldn't make it, we'd have to put too many things for that initiative in the next release, which we'd love to avoid. 
- Risks from adding code late: (to k8s stability, testing, etc.)
  - The change is pretty simple. I don't think there's a notable risk, as long as we keep existing tests (and of course new tests) happy.
- Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
  - This feature is useful to enhance the collaboration between the scheduler and other components (CA etc). Actually, CA maintainers are willing to start using this, and postponing this feature would impact, not only the scheduler, but also such external components development as well. 

Thanks,

Kensei (@sanposhiho)

--
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/CAKSPykCOJtuoMCKwEZ6RAnhCGyXpSFWKWbWyGnkTTjKbT5B7sg%40mail.gmail.com.

--
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/CAPpz9Ytooo-BGdUpZhgM%3DOaPfRmbsOZ9rWzkD_6AUk9M6KQG4Q%40mail.gmail.com.

[Toru Komatsu]

+1 

Also, I have already made the PR for the integration test.
https://github.com/kubernetes/kubernetes/pull/133215

2025年7月25日(金) 20:20 'Dominik Marciński' via sig-scheduling <sig-sch...@kubernetes.io>:

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-scheduling/CAM6GAhEBVoi%3DuxvFfw2%2BcjPWQrE3xLBfm6y67iwHx%2BxOv8L1og%40mail.gmail.com.

[Maciej Skoczeń]

[Kensei Nakada]

[Vyom Yadav]

Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge code + test PRs for this KEP is: 02:00 UTC 30 July.
If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Vyom Yadav
v1.34 Release Team Lead

[0] https://kubernetes.slack.com/archives/C2C40FMNF/p1753469933520519