Skip to content

[WIP] OSDOCS-14688: Improving intro content for Kueue alongside Operator descriptions #94020

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: kueue-docs
Choose a base branch
from
Open

[WIP] OSDOCS-14688: Improving intro content for Kueue alongside Operator descriptions #94020

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 2 additions & 12 deletions welcome/about-kueue.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,19 +6,9 @@ include::_attributes/common-attributes.adoc[]

toc::[]

{product-title} is a Kubernetes-native system that manages access to resources for jobs.
{product-title} can determine when a job waits, is admitted to start by creating pods, or should be _preempted_, meaning that active pods for that job are deleted.
{product-title} is a collection of APIs, based on the link:https://kueue.sigs.k8s.io/docs/[Kueue] open source project, that extends Kubernetes to manage access to resources for jobs.

[NOTE]
====
In the context of {product-title}, a job can be defined as a one-time or on-demand task that runs to completion.
====

{product-title} is based on the link:https://kueue.sigs.k8s.io/docs/[Kueue] open source project.

{product-title} is compatible with environments that use heterogeneous, elastic resources. This means that the environment has many different resource types, and those resources are capable of dynamic scaling.

{product-title} does not replace any existing components in a Kubernetes cluster, but instead integrates with the existing Kubernetes API server, scheduler, and cluster autoscaler components.
{product-title} does not replace any existing components in a Kubernetes cluster, but instead integrates with the existing Kubernetes API server, scheduler, and cluster autoscaler components to determine when a job waits, is admitted to start by creating pods, or should be _preempted_, meaning that active pods for that job are deleted.

{product-title} supports all-or-nothing semantics. This means that either an entire job with all of its components is admitted to the cluster, or the entire job is rejected if it does not fit on the cluster.

Expand Down