<p>A cronjob we scheduled at night was started correctly but the image itself run much later than scheduled. We expect that there was a problem either pulling the image or requesting the resources from the cluster. Usually I can see such errors in the events section of the <code>kubectl describe job-name</code> output. In this section I can see events such as <code>pull image</code> <code>create container</code> etc. But after the job is finished, no events are shown anymore. </p>

<p>Is it possible the see those events for a finished job?</p>

<p>Or is there another way to investigate such a problem?</p>

<p>The problem with storing events is wider than just cronjobs. Events in Kubernetes by default are stored only for 1 hour (--event-ttl flag for kube-apiserver). That means that if your cronjob was run two hours ago - you will not see events in "kubectl describe". </p>

<p>In order to save events for later investigations you need to export them somewhere. For example, Google Kubernetes Engine stores events into Stackdriver. For vanilla Kubernetes you may store events in Prometheus using <a href="https://github.com/caicloud/event_exporter" rel="noreferrer">event_exporter</a> or to <a href="https://github.com/alauda/event-exporter" rel="noreferrer">Elasticsearch</a>. Does that answer your question?</p>
