[Sandbox] Koordinator

[FillZpp]

Application contact emails

FillZpp.wsy@gmail.com, fanster.z@gmail.com

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

• If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

• 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

[nikhita]

@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

[FillZpp]

@nikhita Sure, We are glad to do the presentation. Let's mark on calendar.

[rajaskakodkar]

@FillZpp updated the TAG Runtime agenda with the presentation/discussion date.

[FillZpp]

hi @nikhita @amye , may I ask is there any progress on the TOC sandbox vote on Sept 12?

[raravena80]

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.

• K8s SIG-Scheduling
• K8s Batch Working Group
• Batch System Initiative Working Group(TAG-Runtime)

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!

[hormes]

@raravena80 Is there any update? If you have any concerns, we can arrange an online meeting to discuss it.

[Huang-Wei]

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.

[TheFoxAtWork]

@raravena80 to provide summarization in order for the project to move to the next steps (need-info or vote)