REQUEST: New Slack channel workload-aware-scheduling

[helayoty]

GitHub Username

helayoty

Slack Username

helayoty

What Type of Request is it (Channel, User Group, Bot, Token, or Webhook)?

Channel

Name of Requested Resource

workload-aware-scheduling

Is this request supported by an existing Kubernetes group (SIG, WG, Team, Subproject)? If so, please name them here, and tag a SIG lead who can verify the request.

SIG-Scheduling

Description of Request

Following up the conversation with SIG-Scheduling, SIG-apps, and WG-device-management. The decision is to create a dedicated slack channel for WAS (Workload-aware-scheduling) and TAS (Topology-aware-scheduling) workstream.

cc @mm4tt @johnbelamaric @dom4ha @wojtek-t @kannon92 @andreyvelich

Justification for Request

Many intersections between different sigs and WGs that become to the point hijacking sig-scheduling dedicated topics.

[kannon92]

Can I suggest workload-aware-scheduling instead?

[helayoty]

Can I suggest workload-aware-scheduling instead?

This is my preference as well but how to help community to know that we will discuss topology-aware-scheduling topics here as well?

[andreyvelich]

I think, WAS covers all topics including topology as well, but I agree that it might be confusing for new users.

[helayoty]

@kannon92 @andreyvelich updated.

[kannon92]

Can I suggest workload-aware-scheduling instead?

This is my preference as well but how to help community to know that we will discuss topology-aware-scheduling topics here as well?

https://kubernetes.io/blog/2025/12/29/kubernetes-v1-35-introducing-workload-aware-scheduling/#the-north-star-vision

I think in the description we could put some of the workstreams.

[helayoty]

Can I suggest workload-aware-scheduling instead?

This is my preference as well but how to help community to know that we will discuss topology-aware-scheduling topics here as well?

https://kubernetes.io/blog/2025/12/29/kubernetes-v1-35-introducing-workload-aware-scheduling/#the-north-star-vision

I think in the description we could put some of the workstreams.

Yes, already did.

[kannon92]

Yes, already did.

I meant in the slack channel description.

[palnabarun]

You can raise a PR to create a channel yourself. Please see https://github.com/kubernetes/community/tree/master/communication/slack-config

[helayoty]

You can raise a PR to create a channel yourself. Please see https://github.com/kubernetes/community/tree/master/communication/slack-config

Thank you for the guidance. here you go #8851

[dom4ha]

If we go toward WG, I we were thinking that the group could be focused on WAS integration topics, less on scheduling which could remain rather in sig-scheduling. I would prefer to avoid a situation where scheduling related decisions (algorithms, kube-scheduler architecture changes etc) drift toward WG. This uncertainty is actually one of the blockers how to organize the WG.

In that context, what about calling the channel (and the more or less formal working group) wg-workload-awareness? That would stress more the "awareness" rather than "scheduling" part of WAS?