Skip to content

Conversation

@macsko
Copy link
Member

@macsko macsko commented Oct 30, 2025

Description

This PR add a blog post Workload Aware Scheduling, containing kubernetes/enhancements#4671 and kubernetes/enhancements#5598 features.

Issue

Closes: #

@k8s-ci-robot k8s-ci-robot added the area/blog Issues or PRs related to the Kubernetes Blog subproject label Oct 30, 2025
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 30, 2025
@k8s-ci-robot k8s-ci-robot requested a review from lmktfy October 30, 2025 15:40
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 30, 2025
@macsko macsko marked this pull request as draft October 30, 2025 15:43
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 30, 2025
@netlify
Copy link

netlify bot commented Oct 30, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 9323181
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/693291cd18f6e30008c4eaf5
😎 Deploy Preview https://deploy-preview-53012--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@graz-dev
Copy link
Contributor

graz-dev commented Nov 17, 2025

Hi @macsko 👋 v1.35 Communications team here,

@richabanker as author of #53030, I'd like you to be a writing buddy for @macsko on this PR.

Please:

  • Review this PR, paying attention to the guidelines and review hints
  • Update your own PR based on any best practices you identify that should be applied
  • Remember to be compassionate with your fellow article author

@graz-dev
Copy link
Contributor

Hi @macsko 👋 -- this is Graziano (@graz-dev) from the v1.35 Communications Team!

Just a friendly reminder that we are approaching the feature blog "ready for review" deadline: Friday 21st November. We ask you to have the blog in non-draft state, and all write-up to be complete, so that we can start the blog review from SIG Docs Blog team.

If you have any questions or need help, please don't hesitate to reach out to me or any of the Communications Team members. We are here to help you!

@macsko macsko force-pushed the gang_scheduling_blog branch from 6d6529b to fb9535d Compare November 21, 2025 14:56
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Nov 21, 2025
@macsko macsko changed the title KEP-4671: Gang scheduling blog post KEP-4671, KEP-5598: Introducing Workload Aware Scheduling blog post Nov 21, 2025
@macsko macsko marked this pull request as ready for review November 21, 2025 14:56
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 21, 2025
Copy link
Contributor

@graz-dev graz-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some nits, the overall article looks good and easy to read.
Thank you!

...
```

## How Gang Scheduling Works
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## How Gang Scheduling Works
## How gang scheduling works

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here would be useful to have an example of the behavior.
If you configure this way, and these conditions are met then this will happen...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean modifying the current gang scheduling steps or adding a standalone example after the high level description?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a standalone example after the high level description.

Note that you may need to review your kube-scheduler configuration
to ensure default topology spread constraints are not implicitly disabling batching for your workloads.

See the [docs](TODO) for more details about restrictions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume we should wait for these to land in the dev-1.35 branch?

Exceptions are not hard to get, IMO (the deadline for blog articles is formally today).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think we can merge it as a draft if needed and then add the link to the doc later before publishing it.

@macsko
Copy link
Member Author

macsko commented Nov 24, 2025

/sig scheduling
/cc @dom4ha @sanposhiho @wojtek-t @erictune @bwsalmon

@k8s-ci-robot k8s-ci-robot requested a review from dom4ha November 24, 2025 09:47
@k8s-ci-robot k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Nov 24, 2025
Copy link
Member

@sanposhiho sanposhiho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

technical side from sig-scheduling

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 3, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: 4a7a2a87710f5ce455e8c1765019d78fb5ccec1a

@andreyvelich
Copy link
Member

Looks great, thank you @macsko!
/lgtm

Copy link
Member

@lmktfy lmktfy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

Happy to see this merge as a draft.

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025
@lmktfy
Copy link
Member

lmktfy commented Dec 4, 2025

Oh, it's not passing CI checks.
/approve cancel

@k8s-ci-robot k8s-ci-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025
@macsko macsko force-pushed the gang_scheduling_blog branch from a9b9b29 to 69efb0d Compare December 5, 2025 07:59
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 5, 2025
@k8s-ci-robot k8s-ci-robot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 5, 2025
@macsko macsko force-pushed the gang_scheduling_blog branch from 69efb0d to 9323181 Compare December 5, 2025 08:03
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 5, 2025
@macsko
Copy link
Member Author

macsko commented Dec 5, 2025

@lmktfy It now passed the CI checks

@graz-dev
Copy link
Contributor

graz-dev commented Dec 5, 2025

/lgtm
/approve

Thank you!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 5, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: 7b42b34a3b891e2cf06e15ca14592985092f5ecc

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: graz-dev, sanposhiho

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 5, 2025
@k8s-ci-robot k8s-ci-robot merged commit a890448 into kubernetes:main Dec 5, 2025
6 checks passed
@github-project-automation github-project-automation bot moved this from Needs Final Approver to Done in SIG Scheduling Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

9 participants