Ross ROSS = Recommend OSS · open-source software intelligence for agents

koordinator-sh/koordinator

A QoS-based scheduling system brings optimal layout and status to workloads such as microservices, web services, big data jobs, AI jobs, etc. observed · 2026-08-28

github.com/koordinator-sh/koordinator · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

84/100

  • Activity 99
  • Release rhythm 55
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 166
  • age_days: 1631
  • days_rel: 140
  • days_push: 7
  • n_releases_24m: 4

Full methodology

Adoption not part of the score

1745 stars · 477 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Koordinator is a QoS-based scheduling system for Kubernetes that colocates latency-sensitive microservices with batch, big data, and AI workloads. It improves resource utilization through overcommitment, fine-grained resource isolation, load-aware scheduling, and descheduling while preserving QoS guarantees.

Use cases

  • improve kubernetes cluster resource utilization
  • colocate batch jobs with latency-sensitive microservices
  • run spark and tensorflow jobs alongside web services on kubernetes
  • reduce cloud costs by consolidating workloads
  • schedule pods based on node load and QoS
  • overcommit resources while protecting production SLOs
  • evict and rebalance pods when nodes are overloaded

When to choose

  • you run mixed latency-sensitive and batch workloads on Kubernetes and want higher utilization
  • you need QoS-aware, load-aware scheduling and resource isolation beyond native Kubernetes
  • you want proven production-grade colocation with priority and overcommitment mechanisms

When to avoid

  • you run a small cluster with low utilization where native Kubernetes scheduling suffices
  • you cannot run Linux kernel 4.19+ or deploy DaemonSet node agents
  • you need a scheduler for non-Kubernetes environments

Facets

service · maturity active

container-orchestration scheduling monitoring cloud-computing microservices go self-hosted qos colocation resource-utilization workload-consolidation cost-optimization kubernetes-scheduler descheduler containers devops kubernetes linux docker

9 sources

Member repositories

RepositoryRoleHealth v2
koordinator-sh/koordinatormain84

For agents

markdown · JSON · MCP: product_card(name="koordinator-sh/koordinator")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem