Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Scheduler Configuration Support for AKS #4203

Open
sdesai345 opened this issue Apr 10, 2024 · 5 comments
Open

[Feature] Scheduler Configuration Support for AKS #4203

sdesai345 opened this issue Apr 10, 2024 · 5 comments
Assignees
Labels
feature-request Requested Features

Comments

@sdesai345
Copy link

sdesai345 commented Apr 10, 2024

This feature will provide AKS customers the flexibility and extensibility to change the scheduling mechanism of specific workloads or across an entire cluster. AKS-supported configurations of the Upstream Kubernetes scheduling framework, such as co-scheduling, resource bin-packing to lower cluster costs, custom topology spread, etc. will be detailed in AKS docs.

@stevehipwell
Copy link

REF: kubernetes-sigs/karpenter#1228

@AndrewCi
Copy link

Is there a timeline for this? Would be ideal to be able to set PodTopologyConstraints across the entire cluster https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/#cluster-level-default-constraints by configuring the scheduling profile.

@sdesai345
Copy link
Author

Hi @AndrewCi, we are aiming for public preview release this semester (before Sept).

@fbertos
Copy link

fbertos commented Jun 20, 2024

Having this would be amazing.

Is this planned to be available by September 2024 yet?

Thanks

@sdesai345
Copy link
Author

@fbertos, our team is currently prioritizing security related work, and we anticipate some changes in the development/release timeline - we will update the roadmap for this feature to "in progress" once the design can begin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Requested Features
Projects
Development

No branches or pull requests

4 participants