Kubernetes
foundation · United StatesScores
1 product on the map — 1 open.
Openness
5 high confidence- license
- Apache-2.0(OSI)
- source
- public(kubernetes-sigs/kueue is the whole controller)
- core features withheld
- no — a 15,902-entry recursive tree carries no path matching enterprise, ee, commercial or proprietary
Kueue is Apache-2.0 and installs whole on a plain Kubernetes cluster, with no paid tier for a core to be withheld from. The repository tree carries one root LICENSE and no enterprise, ee or commercial path.
- https://api.github.com/repos/kubernetes-sigs/kueue/git/trees/main?recursive=1 recorded 2026-09-15
Full untruncated recursive tree of the default branch, 15,902 entries. Licenses are the root LICENSE and vendored dependencies. No path matches enterprise, ee, commercial or proprietary. A tree lists paths; it is cited for that and for nothing about the vendor's offerings.
- https://github.com/kubernetes-sigs/kueue recorded 2026-09-15
Repository page for kubernetes-sigs/kueue: Apache-2.0 license, public and unarchived, described as 'Kubernetes-native Job Queueing'. Establishes the license and that the source is public.
- https://kueue.sigs.k8s.io/docs/overview/ recorded 2026-09-16
Kueue's overview: 'You can install Kueue on top of a vanilla Kubernetes cluster' and 'Kueue does not replace any existing Kubernetes components.' A Kubernetes SIG project with no vendor edition; the installable thing is the whole thing.
Adoption
2 low confidenceKueue ships as container images and a Helm chart rather than through a package registry, so GitHub stars are the only adoption signal available. A star is not a use, so the signal shows attention rather than real usage.
- https://github.com/kubernetes-sigs/kueue recorded 2026-09-15
Repository page showing 2,971 GitHub stars for kubernetes-sigs/kueue.
Capability
5 medium confidenceKueue's Topology-Aware Scheduling does the placing, not its queueing alone: it can fix an assignment of pods to nodes and inject a NodeSelector, and podset-required-topology can bind a whole set to one rack or block. Kueue makes that placement decision itself, with Kubernetes only executing it, which puts it level with Volcano.
- https://kueue.sigs.k8s.io/docs/concepts/topology_aware_scheduling/ recorded 2026-09-15
Kueue's Topology-Aware Scheduling concept page: 'When the lowest level of Topology is set to node, TAS finds a fixed assignment of pods to nodes and injects a NodeSelector to make sure the pods get scheduled on the selected nodes', and the podset-required-topology annotation requiring all pods within one topology domain.
- https://kueue.sigs.k8s.io/docs/overview/ recorded 2026-09-15
Kueue overview: 'Kueue decides when a job should wait, when a job should be admitted to start (as in pods can be created) and when a job should be preempted', with quotas, fair sharing and resource fungibility across flavors.