OSDOCS-13820: Adding Kueue about docs

Author: abrennan89

_attributes/common-attributes.adoc

@@ -21,14 +21,6 @@
 :op-system-base-full: Red Hat Enterprise Linux (RHEL)
 :op-system-version: 9.x
 :op-system-version-9: 9
-ifdef::openshift-origin[]
-:op-system-first: Fedora CoreOS (FCOS)
-:op-system: FCOS
-:op-system-lowercase: fcos
-:op-system-base: Fedora
-:op-system-base-full: Fedora
-:op-system-version: 35
-endif::[]
 :tsb-name: Template Service Broker
 :kebab: image:kebab.png[title="Options menu"]
 :ai-full: Assisted Installer
@@ -144,3 +136,5 @@ endif::[]
 :mce-short: multicluster engine Operator
 //Kueue
 :kueue-s: Kueue
+:kueue-op: Kueue Operator
+:ocp-full: Red Hat OpenShift Container Platform

_topic_maps/_topic_map.yml

@@ -29,3 +29,5 @@ Distros: openshift-kueue
 Topics:
 - Name: Welcome
   File: index
+- Name: About Red Hat OpenShift Build of Kueue
+  File: about-kueue

about/about-kueue.adoc

@@ -0,0 +1,37 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="about-kueue"]
+= About {product-title}
+:context: about-kueue
+
+toc::[]
+
+{product-title} is a Kubernetes-native system that manages quotas and how jobs consume them. Kueue decides when a job waits, when a job is admitted to start by creating pods, and when a job should be _preempted_ (active pods should be deleted).
+
+Kueue 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.
+
+// Personas
+[id="about-kueue-personas"]
+== {kueue-s} personas
+
+Different personas exist in a {kueue-s} workflow.
+
+Batch administrators:: manage the cluster infrastructure and establish quotas and queues.
+Batch users:: runs workloads. Examples of batch users might be researchers, AI/ML engineers, or data scientists.
+Serving users:: runs workloads, for example, to expose a trained AI/ML model for inference.
+Platform developers:: integrates Kueue with other software. Might contribute to the upstream Kueue project.
+
+// How it works
+[id="about-kueue-workflow"]
+== {kueue-s} workflow
+// TODO: add diagram?
+
+The {kueue-s} workflow can be described at a high level as follows:
+
+. Batch administrators create and configure resource flavors and queues.
+. User personas create jobs on the cluster.
+. The `kube-apiserver` component validates and accepts job data.
+. Kueue admits jobs based on configured options, such as order or quota.
+. The job controller creates pods.
+. The `kube-scheduler` component assigns pods to a node in the cluster.
+. The `cluster-autoscaler` component provisions more nodes as required.

welcome/about-kueue.adoc

@@ -0,0 +1,48 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="about-kueue"]
+= About {product-title}
+:context: about-kueue
+
+toc::[]
+
+//What is kueue?
+{product-title} is a job and resource management system for {ocp-full} clusters.
+
+// Who should / when should someone use Kueue?
+{kueue-s} 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.
+
+// Personas
+[id="about-kueue-personas"]
+== {kueue-s} personas
+
+There are two different personas used in a {kueue-s} workflow; batch administrators, and batch users.
+
+A batch administrator manages the cluster infrastructure and establishes quotas and queues.
+
+As a batch administrator, you can complete the following tasks:
+
+- Setup role-based access control to Kueue objects.
+- Administer cluster quotas by using cluster queues and local queues.
+- Setup "all-or-nothing" with ready pods.
+- Monitor pending workloads.
+- Run Kueue-managed jobs with a custom workload priorities.
+- Setup a multi-Kueue environment.
+- Use a third-party certificate authority with Kueue.
+
+// How it works
+[id="about-kueue-workflow"]
+== {kueue-s} workflow
+
+// TODO: add diagram
+
+The {kueue-s} workflow can be described at a high level as follows:
+
+. Batch administrators create and configure resource flavors and queues.
+. Batch users create jobs on the cluster.
+. The `kube-apiserver` component validates and accepts job data.
+. {kueue-s} admits jobs based on configured options, such as order or quota.
+// how does nodeaffinity work
+. The job controller creates pods.
+. The `kube-scheduler` component assigns pods to a node in the cluster.
+. The `cluster-autoscaler` component provisions more nodes as required.