<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Job on The IT Hollow</title>
    <link>https://theithollow.com/tags/job/</link>
    <description>Recent content in Job on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Dec 2019 15:05:36 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/job/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Jobs and CronJobs</title>
      <link>https://theithollow.com/2019/12/16/kubernetes-jobs-and-cronjobs/</link>
      <pubDate>Mon, 16 Dec 2019 15:05:36 +0000</pubDate>
      <guid>https://theithollow.com/2019/12/16/kubernetes-jobs-and-cronjobs/</guid>
      <description>&lt;p&gt;Sometimes we need to run a container to do a specific task, and when its completed, we want it to quit. Many containers are deployed and continuously run, such as a web server. But other times we want to accomplish a single task and then quit. This is where a Job is a good choice.&lt;/p&gt;
&lt;h2 id=&#34;jobs-and-cronjobs---the-theory&#34;&gt;Jobs and CronJobs - The Theory&lt;/h2&gt;
&lt;p&gt;Perhaps, we need to run a batch process on demand. Maybe we built an automation routine for something and want to kick it off through the use of a container. We can do this by submitting a job to the Kubernetes API. Kubernetes will run the job to completion and then quit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
