<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tasks on Jobset</title><link>/docs/tasks/</link><description>Recent content in Tasks on Jobset</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 13 Jan 2026 20:49:35 +0000</lastBuildDate><atom:link href="/docs/tasks/index.xml" rel="self" type="application/rss+xml"/><item><title>Example Workloads</title><link>/docs/tasks/workload_examples/</link><pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate><guid>/docs/tasks/workload_examples/</guid><description>&lt;h2 id="pytorch-example">PyTorch Example&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://github.com/kubernetes-sigs/jobset/tree/main/site/static/examples/pytorch/cnn-mnist/mnist.yaml">Distributed Training of a CNN on the MNIST dataset using PyTorch and JobSet&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Note&lt;/strong>: Machine learning container images can be quite large so it may take some time to pull the images.&lt;/p>
&lt;h2 id="tensorflow-example">TensorFlow Example&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://github.com/kubernetes-sigs/jobset/tree/main/site/static/examples/tensorflow/mnist.yaml">Distributed Training of a Handwritten Digit Classifier on the MNIST dataset using TensorFlow and JobSet&lt;/a>&lt;/li>
&lt;/ul>
&lt;p>This example runs an example job for a single epoch.
You can view the progress of your jobs via &lt;code>kubectl logs jobs/tensorflow-tensorflow-0&lt;/code>.&lt;/p></description></item><item><title>Simple Examples</title><link>/docs/tasks/simple_examples/</link><pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate><guid>/docs/tasks/simple_examples/</guid><description>&lt;p>Here we have some simple examples demonstrating core JobSet features.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;a href="https://github.com/kubernetes-sigs/jobset/tree/main/site/static/examples/simple/success-policy.yaml">Success Policy&lt;/a> demonstrates an example of utilizing &lt;code>successPolicy&lt;/code>.
Success Policy allows one to specify when to mark a JobSet as completed successfully.
This example showcases how to use success policy to mark the JobSet as successful if the worker replicated job completes.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;a href="https://github.com/kubernetes-sigs/jobset/blob/main/site/static/examples/simple/exclusive-placement.yaml">Exclusive Job Placement&lt;/a>
demonstrates how to configure a JobSet to have a 1:1 mapping between each child Job and a particular topology domain, such as a datacenter rack or zone. This means that all the pods belonging to a child job will be colocated in the same topology domain, while pods from other jobs will not be allowed to run within this domain. This gives the child job exclusive access to computer resources in this domain.&lt;/p></description></item><item><title>Failure Policy</title><link>/docs/tasks/failure_policy/</link><pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate><guid>/docs/tasks/failure_policy/</guid><description>&lt;p>JobSet provides failure policy API to control how your workload behaves in response to child Job failures.&lt;/p>
&lt;p>The &lt;code>failurePolicy&lt;/code> is defined by a set of &lt;code>rules&lt;/code>. For any job failure, the rules are evaluated in order, and the first matching rule&amp;rsquo;s action is executed. If no rule matches, the default action is &lt;code>RestartJobSet&lt;/code>, which counts towards the &lt;code>maxRestarts&lt;/code> limit.&lt;/p>
&lt;h2 id="failure-policy-actions">Failure Policy Actions&lt;/h2>
&lt;h3 id="failjobset">&lt;code>FailJobSet&lt;/code>&lt;/h3>
&lt;p>This action immediately marks the entire JobSet as failed.&lt;/p></description></item><item><title>Volume Claim Policies</title><link>/docs/tasks/volume_claim_policies/</link><pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate><guid>/docs/tasks/volume_claim_policies/</guid><description>&lt;p>JobSet provides the VolumeClaimPolicies API to automatically create and manage shared
PersistentVolumeClaims (PVCs) across multiple ReplicatedJobs within a JobSet.
This enables stateful JobSets that require persistent storage for datasets, models, checkpoints, or
intermediate results.&lt;/p>
&lt;h2 id="basic-usage">Basic Usage&lt;/h2>
&lt;p>To use VolumeClaimPolicies, define them in the &lt;code>volumeClaimPolicies&lt;/code> field of your JobSet spec.
Each policy can contain one or more PVC templates.&lt;/p>
&lt;p>&lt;a href="https://github.com/kubernetes-sigs/jobset/blob/main/site/static/examples/volume-claim-policy/single-pvc.yaml">This example&lt;/a>
demonstrates creating shared PVCs with different retention policies:&lt;/p>
&lt;p>In this example:&lt;/p></description></item></channel></rss>