<?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://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/</link>
		<description>Recent content in Admission Check on Kueue</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 27 Oct 2025 10:53:37 -0400</lastBuildDate>
		
			<atom:link href="https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>ProvisioningRequest</title>
				<link>https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/provisioning_request/</link>
				<pubDate>Mon, 23 Oct 2023 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/provisioning_request/</guid>
				<description>&lt;p&gt;When AdmissionChecks or &lt;a href=&#34;https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/topology_aware_scheduling/&#34;&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=&#34;https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/provisioning_request/#provisioning-admissioncheck-controller&#34;&gt;ProvisioningRequest AdmissionCheck&lt;/a&gt; addresses this in cluster-autoscaler environments.&lt;/p&gt;&#xA;&lt;p&gt;Kueue&amp;rsquo;s enhanced admission requires two sequential checks:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&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://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/multikueue/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/multikueue/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/multikueue/&#34;&gt;MultiKueue&lt;/a&gt; &lt;a href=&#34;https://deploy-preview-12213--kubernetes-sigs-kueue.netlify.app/docs/concepts/admission_check/&#34;&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>
