Update KEP-77 with additional details and focus on batchv1/Job

[ichekrygin]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR updates the already accepted KEP-77 by fleshing out additional design details and aligning it with recent changes and constructs in Kueue. These updates provide a clearer path for both contributors and reviewers and reflect the current direction of the implementation.

Which issue(s) this PR fixes:

Fixes #5527

Special notes for your reviewer:

This PR enhances KEP-77 by expanding on the design to support batch/v1.Job horizontal scaling and aligning terminology and workflows with current Kueue capabilities.

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

Hi @ichekrygin. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	af1e7e6
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/687e62465cc27d0007d276c4

[mimowo]

/ok-to-test

[mimowo]

I'm planning to review this early next week.

[mimowo]

First pass, but it LGTM as for Alpha IMO.

cc @tenzen-y

[ichekrygin]

Thank you, @mimowo, for the detailed review and insights. I’ve addressed and/or responded to all the comments in your review. Could you please take another look when you have a moment?

[mimowo]

We only add release notes to PRs which directly have user-facing consequences.
/release-note-edit

NONE

[mimowo]

I'm thinking about renaming the feature (and associated things like feature gate or KEP title) from DynamicallySizedJobs to ElasticJobs. It is shorter to pronounce and captures the very same idea.

Wdyt @tenzen-y @ichekrygin ?

[ichekrygin]

I'm thinking about renaming the feature (and associated things like feature gate or KEP title) from DynamicallySizedJobs to ElasticJobs. It is shorter to pronounce and captures the very same idea.

Wdyt @tenzen-y @ichekrygin ?

ElasticJobs SGTM, as long as we use WorkloadSlices as the implementation detail.

[ichekrygin]

Hello @mimowo @tenzen-y thank you for the review and feedback.
I have reviewed all comments and updated KEP per provided feed back.

Note: WorkloadSliceReplacement -> WorkloadSliceReplaced change was discussed in the context of #5510.

[mimowo]

Thank you! It is a complex, but long awaited KEP :) The number 77 says everything, I'm super happy you took the challenge.

/lgtm
/approve
Leaving final tagging to @tenzen-y
/hold

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: da4dd0a6729042ce86b2bbe045daced832609f4b

[tenzen-y]

Thank you for this awesome work!
/lgtm
/approve

/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ichekrygin, mimowo, tenzen-y

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:

• OWNERS [mimowo,tenzen-y]

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