<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on Ricky Moorhouse</title>
    <link>https://rickymoorhouse.uk/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Ricky Moorhouse</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 20 Jul 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rickymoorhouse.uk/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debugging jobs in kubernetes</title>
      <link>https://rickymoorhouse.uk/blog/2021/debugging-jobs-in-k8s/</link>
      <pubDate>Tue, 20 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2021/debugging-jobs-in-k8s/</guid>
      <description>&lt;p&gt;As jobs are often short running and finish before you can check anything within the pod, often it&#39;s helpful to make the pod run for longer to be able to inspect the environment and re-run the job manually.&#xA;One way to do this is to extract the yaml definition for a previous run of the job and create a pod definition replacing the command with an endless sleep.&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;kubectl get pod {previous-job-pod} -o yaml &amp;gt; pod.yaml&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;Then edit the pod.yaml, removing the &lt;code&gt;status&lt;/code&gt; block and the additional metadata referring to the previous job so the metadata only contains name and namespace&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
