instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from the Job terminates with success, no new Pods are created.once at least one Pod has terminated with success and all Pods are terminated,
  then the Job is completed with success.once any Pod has exited with success, no other Pod should still be doing any work
  for this task or writing any output. They should all be in the process of exiting.For a non-parallel Job, you can leave both .spec.completions and .spec.parallelism unset.
  When both are unset, both are defaulted to 1.For a fixed completion count Job, you should set .spec.completions to the number of completions needed.
  You can set .spec.parallelism, or leave it unset and it will default to 1.For a work queue Job, you must leave .spec.completions unset, and set .spec.parallelism to
  a non-negative integer.For more information about how to make use of the different types of job,
  see the job patterns section.Controlling parallelismThe requested parallelism (.spec.parallelism) can be set to any non-negative value.
  If it is unspecified, it defaults to 1.
  If it is specified as 0, then the Job is effectively paused until it is increased.Actual parallelism (number of pods running at any instant) may be more or less than requested
  parallelism, for a variety of reasons:For fixed completion count Jobs, the actual number of pods running in parallel will not exceed the number of
  remaining completions. Higher values of .spec.parallelism are effectively ignored.For work queue Jobs, no new Pods are started after any Pod has succeeded -- remaining Pods are allowed to complete, however.If the Job Controller has not had time to react.If the Job controller failed to create Pods for any reason (lack of ResourceQuota, lack of permission, etc.),
  then there may be fewer pods than requested.The Job controller may throttle new Pod creation due to excessive previous pod failures in the same Job.When a Pod is gracefully shut down, it takes time to stop.Completion modeFEATURE STATE:
  Kubernetes v1.24 [stable]Jobs with fixed completion count - that is, jobs that have non 
  .spec.completions - can have a completion mode that is specified in .spec.completionMode:NonIndexed (default): the Job is considered complete when there have been
  .spec.completions successfully completed Pods. In other words, each Pod
  completion is homologous to each other. Note that Jobs that have 
  .spec.completions are implicitly NonIndexed.Indexed: the Pods of a Job get an associated completion index
  ```