<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Admission Check on Kueue</title><link>https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/</link><description>Recent content in Admission Check on Kueue</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 00:10:19 -0700</lastBuildDate><atom:link href="https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/index.xml" rel="self" type="application/rss+xml"/><item><title>ProvisioningRequest</title><link>https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/provisioning_request/</link><pubDate>Mon, 23 Oct 2023 00:00:00 +0000</pubDate><guid>https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/provisioning_request/</guid><description>&lt;p&gt;When AdmissionChecks or &lt;a href="https://kueue.sigs.k8s.io/docs/concepts/topology_aware_scheduling/"&gt;TopologyAwareScheduling&lt;/a&gt; were not configured, Admissions were mainly based on quota checks - if sufficient quota existed, Kueue admitted the Workload. While quota reservation confirmed logical resource availability, it didn&amp;rsquo;t guarantee that physical resources existed to schedule all Pods successfully. The &lt;a href="https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/provisioning_request/#provisioning-admissioncheck-controller"&gt;ProvisioningRequest AdmissionCheck&lt;/a&gt; addresses this in cluster-autoscaler environments.&lt;/p&gt;
&lt;p&gt;Kueue&amp;rsquo;s enhanced admission requires two sequential checks:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Quota Reservation:&lt;/strong&gt; Kueue validates the resource requests against ClusterQueue&amp;rsquo;s available quota and resource flavors, reserves the required resources if available and locks the quota to prevent other Workloads from claiming it. This step verifies logical resource availability.&lt;/p&gt;</description></item><item><title>Multikueue</title><link>https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/multikueue/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/multikueue/</guid><description>&lt;p&gt;&lt;a href="https://kueue.sigs.k8s.io/v0.18/docs/concepts/multikueue/"&gt;MultiKueue&lt;/a&gt; &lt;a href="https://kueue.sigs.k8s.io/v0.18/docs/concepts/admission_check/"&gt;AdmissionCheck&lt;/a&gt; is the central component responsible for admission of workloads created on the management cluster, based on their of the workloads on the selected worker cluster.&lt;/p&gt;</description></item></channel></rss>