sandbox
sandbox copied to clipboard
cncf
[Sandbox] Koordinator
Application contact emails
[email protected], [email protected]
Project Summary
A QoS-based scheduling system brings optimal layout and status to workloads such as microservices, web services, big data jobs, AI jobs, etc.
Project Description
Koordinator is a QoS based scheduling system for hybrid orchestration workloads on Kubernetes. Its goal is to improve the runtime efficiency and reliability of both latency sensitive workloads and batch jobs, simplify the complexity of resource-related configuration tuning, and increase pod deployment density to improve resource utilization.
Koordinator enhances the kubernetes user experiences in the workload management by providing the following:
- Improved Resource Utilization: Koordinator is designed to optimize the utilization of cluster resources, ensuring that all nodes are used effectively and efficiently.
- Enhanced Performance: By using advanced algorithms and techniques, Koordinator aims to improve the performance of Kubernetes clusters, reducing interference between containers and increasing the overall speed of the system.
- Flexible Scheduling Policies: Koordinator provides a range of options for customizing scheduling policies, allowing administrators to fine-tune the behavior of the system to suit their specific needs.
- Easy Integration: Koordinator is designed to be easy to integrate into existing Kubernetes clusters, allowing users to start using it quickly and with minimal hassle.
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/koordinator-sh
Project repo URL in scope of application
https://github.com/koordinator-sh/koordinator
Additional repos in scope of the application
https://github.com/koordinator-sh/community https://github.com/koordinator-sh/apis https://github.com/koordinator-sh/koordetector https://github.com/koordinator-sh/website https://github.com/koordinator-sh/charts
Website URL
https://koordinator.sh/
Roadmap
https://github.com/koordinator-sh/community/blob/main/roadmap.md
Roadmap context
No response
Contributing Guide
https://github.com/koordinator-sh/koordinator/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/koordinator-sh/koordinator/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/koordinator-sh/koordinator/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
Alibaba Cloud
Maintainers file
https://github.com/koordinator-sh/community/blob/main/MAINTAINERS.md
IP Policy
- [X] If the project is accepted, I agree the project will follow the CNCF IP Policy
Trademark and accounts
- [X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF
Why CNCF?
The CNCF hosts a vibrant and diverse community of developers and organizations. Contributing to this ecosystem allows the Koordinator project to attract more contributors, leading to better and faster improvements. Furthermore, the CNCF is able to provide a vendor neutral home for the project, allowing for collaboration among various vendors, fostering the creation of a solution that delivers collective benefits to all stakeholders within the ecosystem.
Benefit to the Landscape
Koordinator provides a well-designed hybrid orchestration and SLO system for both serverless and batch workloads on Kubernetes. It facilitates users by optimize the utilization of their cluster resources, ensuring that all nodes are used effectively and efficiently. Simultaneously, it provides a range of options for customizing scheduling policies, allowing administrators to fine-tune the behavior of the system to suit their specific needs.
Cloud Native 'Fit'
The Koordinator best fits in under the "Scheduling and Orchestration" area of the landscape.
Cloud Native 'Integration'
The project should be installed and as a scheduler/operator in Kubernetes.
Cloud Native Overlap
There is no strong overlap with existing solutions that mainly focuses on hybrid orchestration scheduling and enhanced SLO management. Volcano, one of the CNCF projects, on the other hand, is mainly for those batch jobs scheduling and management.
Similar projects
Volcano may be, but they focus on different scheduling targets and areas.
Landscape
Yes, it's already in the "Scheduling & Orchestration".
Business Product or Service to Project separation
N/A
Project presentations
No response
Project champions
No response
Additional information
No response
@FillZpp It'd be great if you could present Koordinator at a TAG Runtime meeting before the next TOC sandbox vote on Sept 12.
cc @raravena80 @helayoty @rajaskakodkar
hi @nikhita @amye , may I ask is there any progress on the TOC sandbox vote on Sept 12?
Hi @FillZpp, thanks for the follow up.
Not precluding the possibility that Koordinator can be a CNCF Sandbox project, there was a doubt with regards to how this project fits into the CNCF/K8s ecosystem.
The recommendation/consensus was (before voting for Koordinator as a CNCF Sandbox project) to reach out to (or communicate with) the following groups within the CNCF/K8s ecosystem to check if the project fits better into either the CNCF or the K8s ecosystem.
Then come back with the outcome and proceed from there.
Feel free to reach out either here or on the CNCF slack if you have any other specific questions.
Thanks!
@raravena80 Is there any update? If you have any concerns, we can arrange an online meeting to discuss it.
Per my understanding on Koordinaor, its stack involves both scheduling and runtime, and even more. Shaping it as a sub-project of sig-scheduling does't quite reveal its accurate scope. My 2 cents is that a standalone sandbox project makes more sense to Koordinator.
@raravena80 to provide summarization in order for the project to move to the next steps (need-info or vote)
Based on the 'no concerns' from K8s SIG-Scheduling, as a next step before the Jan 23 sandbox application review, I'd like to request if there are any concerns from the following community members:
- K8s Batch
- @Huang-Wei
- @endocrimes
- @mwielgus
- @soltysh
- @swatisehgal
- WG BSI
- @stackedsax
- @k82cn
- @yangwwei
If there are aren't any before the meeting. I see no issues with the sandbox application and say that the project is ready for a vote.
Thanks!
That looks good to me :).
A sandbox seems better for Koordinator instead of sub-project of k8s sigs, as it includes several enhancement cross different components.
For k8s wg-batch, I'd suggest showing up to one of the first calls in Jan and discuss with the broader community there.
@FillZpp following up. Were you able to connect with wg-batch? Thanks!
@rajaskakodkar @amye I have introduced the project and discussed with wg-batch broader community yesterday. We have reached an agreement that Koordinator is ready for a sandbox vote.
Vote created
@castrojo has called for a vote on [Sandbox] Koordinator (#51).
The members of the following teams have binding votes:
| Team |
|---|
| @cncf/cncf-toc |
Non-binding votes are also appreciated as a sign of support!
How to vote
You can cast your vote by reacting to this comment. The following reactions are supported:
| In favor | Against | Abstain |
|---|---|---|
| 👍 | 👎 | 👀 |
Please note that voting for multiple options is not allowed and those votes won't be counted.
The vote will be open for 7days. It will pass if at least 66% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.
![git-vote[bot] avatar](https://avatars.githubusercontent.com/in/206179?v=4 "Published by a pub.dev verified publisher"){kind=small}
Vote status
So far 45.45% of the users with binding vote are in favor (passing threshold: 66%).
Summary
| In favor | Against | Abstain | Not voted |
|---|---|---|---|
| 5 | 0 | 0 | 6 |
Binding votes (5)
| User | Vote | Timestamp |
|---|---|---|
| TheFoxAtWork | In favor | 2024-04-09 21:50:33.0 +00:00:00 |
| dims | In favor | 2024-04-09 17:37:34.0 +00:00:00 |
| kgamanji | In favor | 2024-04-10 16:17:38.0 +00:00:00 |
| rochaporto | In favor | 2024-04-09 18:40:31.0 +00:00:00 |
| cathyhongzhang | In favor | 2024-04-09 16:13:11.0 +00:00:00 |
| @mauilion | Pending | |
| @linsun | Pending | |
| @dzolotusky | Pending | |
| @kevin-wangzefeng | Pending | |
| @nikhita | Pending | |
| @erinaboyd | Pending |
Non-binding votes (1)
| User | Vote | Timestamp |
|---|---|---|
| Huang-Wei | In favor | 2024-04-09 16:52:14.0 +00:00:00 |
Vote status
So far 63.64% of the users with binding vote are in favor (passing threshold: 66%).
Summary
| In favor | Against | Abstain | Not voted |
|---|---|---|---|
| 7 | 0 | 0 | 4 |
Binding votes (7)
| User | Vote | Timestamp |
|---|---|---|
| linsun | In favor | 2024-04-11 10:36:48.0 +00:00:00 |
| cathyhongzhang | In favor | 2024-04-09 16:13:11.0 +00:00:00 |
| dims | In favor | 2024-04-09 17:37:34.0 +00:00:00 |
| nikhita | In favor | 2024-04-12 9:29:31.0 +00:00:00 |
| kgamanji | In favor | 2024-04-10 16:17:38.0 +00:00:00 |
| rochaporto | In favor | 2024-04-09 18:40:31.0 +00:00:00 |
| TheFoxAtWork | In favor | 2024-04-09 21:50:33.0 +00:00:00 |
| @mauilion | Pending | |
| @dzolotusky | Pending | |
| @kevin-wangzefeng | Pending | |
| @erinaboyd | Pending |
Non-binding votes (3)
| User | Vote | Timestamp |
|---|---|---|
| Huang-Wei | In favor | 2024-04-09 16:52:14.0 +00:00:00 |
| FillZpp | In favor | 2024-04-11 8:08:39.0 +00:00:00 |
| saintube | In favor | 2024-04-11 8:20:43.0 +00:00:00 |
Vote status
So far 63.64% of the users with binding vote are in favor (passing threshold: 66%).
Summary
| In favor | Against | Abstain | Not voted |
|---|---|---|---|
| 7 | 0 | 0 | 4 |
Binding votes (7)
| User | Vote | Timestamp |
|---|---|---|
| rochaporto | In favor | 2024-04-09 18:40:31.0 +00:00:00 |
| kgamanji | In favor | 2024-04-10 16:17:38.0 +00:00:00 |
| cathyhongzhang | In favor | 2024-04-09 16:13:11.0 +00:00:00 |
| linsun | In favor | 2024-04-11 10:36:48.0 +00:00:00 |
| nikhita | In favor | 2024-04-12 9:29:31.0 +00:00:00 |
| dims | In favor | 2024-04-09 17:37:34.0 +00:00:00 |
| TheFoxAtWork | In favor | 2024-04-09 21:50:33.0 +00:00:00 |
| @mauilion | Pending | |
| @dzolotusky | Pending | |
| @kevin-wangzefeng | Pending | |
| @erinaboyd | Pending |
Non-binding votes (4)
| User | Vote | Timestamp |
|---|---|---|
| Huang-Wei | In favor | 2024-04-09 16:52:14.0 +00:00:00 |
| FillZpp | In favor | 2024-04-11 8:08:39.0 +00:00:00 |
| saintube | In favor | 2024-04-11 8:20:43.0 +00:00:00 |
| eahydra | In favor | 2024-04-13 8:34:30.0 +00:00:00 |
Vote closed
The vote passed! 🎉
72.73% of the users with binding vote were in favor (passing threshold: 66%).
Summary
| In favor | Against | Abstain | Not voted |
|---|---|---|---|
| 8 | 0 | 0 | 3 |
Binding votes (8)
| User | Vote | Timestamp |
|---|---|---|
| @TheFoxAtWork | In favor | 2024-04-09 21:50:33.0 +00:00:00 |
| @dzolotusky | In favor | 2024-04-15 18:26:22.0 +00:00:00 |
| @dims | In favor | 2024-04-09 17:37:34.0 +00:00:00 |
| @linsun | In favor | 2024-04-11 10:36:48.0 +00:00:00 |
| @cathyhongzhang | In favor | 2024-04-09 16:13:11.0 +00:00:00 |
| @rochaporto | In favor | 2024-04-09 18:40:31.0 +00:00:00 |
| @nikhita | In favor | 2024-04-12 9:29:31.0 +00:00:00 |
| @kgamanji | In favor | 2024-04-10 16:17:38.0 +00:00:00 |
Non-binding votes (5)
| User | Vote | Timestamp |
|---|---|---|
| @Huang-Wei | In favor | 2024-04-09 16:52:14.0 +00:00:00 |
| @FillZpp | In favor | 2024-04-11 8:08:39.0 +00:00:00 |
| @saintube | In favor | 2024-04-11 8:20:43.0 +00:00:00 |
| @eahydra | In favor | 2024-04-13 8:34:30.0 +00:00:00 |
| @hormes | In favor | 2024-04-16 7:11:50.0 +00:00:00 |
Heya @FillZpp!
Welcome aboard! We're very excited to get you onboarded as a CNCF sandbox project! Here's the link to your onboarding checklist: https://github.com/cncf/sandbox/issues/144
That issue is where you can communicate any questions or concerns you might have. Please don't hesitate to reach out!
With the onboarding issue open at: https://github.com/cncf/sandbox/issues/144 I'm going to go ahead and close this out. 👍
Thanks!
