Changes

Note that there are timeouts in place - this is a demo pod which runs only for 24 hours and an interactive session also has a time limit, so it is better to build a custom run script which is executed when the container in the pod starts. A job is a wrapper for a pod spec, which can for example make sure that the pod is restarted until it has at least one successful completion. This is useful for long deep learning work loads, where a pod failure might happen in between (for example due to a node reboot). See the [https://kubernetes.io/docs/concepts/workloads/pods/ Kubernetes documentation on docs for pods and ] or [https://kubernetes.io/docs/concepts/workloads/controllers/job/ jobs ] for more details. TODO: link to respective doc.