<p>Is it possible to test whether there is a node with sufficient resources before starting a job?</p>

micha
<p>I think that depends on the environment you are building (from my experience).</p>
<p>Disk space, process power and memory can be easily tracked.</p>
<p>From the control plane you can install kubernetes/metrics-server and use</p>
<pre><code>kubectl top nodes
</code></pre>
<p>for the current situation of the nodes.
Also if you have local volume provisioning via blockDevices (eq. openebs-cstore)
You can always use</p>
<pre><code>kubectl get bd --all-namespaces
</code></pre>
<p>to see the available blockdevices or if you have cstore pools</p>
<pre><code>kubectl get csp --all-namespaces
</code></pre>
<p>to check the allocation process and capacity on the disks.</p>
<p>EQ.</p>
<pre><code>NAME                   ALLOCATED   FREE    CAPACITY   STATUS    READONLY   TYPE      AGE
cstor-disk-pool-1tgd   264K        19.9G   19.9G      Healthy   false      striped   22h
cstor-disk-pool-3cvq   393K        19.9G   19.9G      Healthy   false      striped   22h
cstor-disk-pool-coq6   254K        9.94G   9.94G      Healthy   false      striped   22h
</code></pre>
<p>In the local version these information are avaliable and useful (for me at least).</p>
<p>Once you check these resources if you have a deployment definition with resource claims (cpu and memory included) you can decide whether you need more or less of a specific resource.</p>
<p>Also you can create a test environment to freely test the deployment (with higher resources) and than decide the cluster or the node you want to use.</p>
