<p>All</p>

<p>have kubernetes on Google Computing Engine running, launching pods etc.</p>

<p>Recently learned that in Kubernetes Jobs were added as first class construct.</p>

<p>Could someone enlighten me why they were added? Looks like another level of indirection, but to solve exactly WHAT kind of problems which pods and replication controller were unable to solve?</p>

<p>Jobs are for workloads designed for tasks that will run to completion, then exit.</p>

<p>It is technically still a pod, just another kind. Where a pod while start up and run continuously until it's terminated or it crashes, a job will run a workload, then it will exit with a "Completed" status.</p>

<p>There is also a cronJob type, which will run periodically on set times. If you think of how cronJobs work on a standard Linux system, it should give you an idea of how you might utilize jobs (or cronJobs) on your k8s cluster</p>
