instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from each Pod in the returned list.View the standard output of one of the pods:kubectl logs $pods
  Another way to view the logs of a Job:kubectl logs jobs/pi
  The output is similar to this:3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901
  Writing a Job specAs with all other Kubernetes config, a Job needs apiVersion, kind, and metadata fields.When the control plane creates new Pods for a Job, the .metadata.name of the
  Job is part of the basis for naming those Pods. The name of a Job must be a valid
  DNS subdomain
  value, but this can produce unexpected results for the Pod hostnames. For best compatibility,
  the name should follow the more restrictive rules for a
  DNS label.
  Even when the name is a DNS subdomain, the name must be no longer than 63
  characters.A Job also needs a .spec section.Job LabelsJob labels will have batch.kubernetes.io/ prefix for job-name and controller-uid.Pod TemplateThe .spec.template is the only required field of the .spec.The .spec.template is a pod template.
  It has exactly the same schema as a Pod,
  except it is nested and does not have an apiVersion or kind.In addition to required fields for a Pod, a pod template in a Job must specify appropriate
  labels (see pod selector) and an appropriate restart policy.Only a RestartPolicy
  equal to Never or OnFailure is allowed.Pod selectorThe .spec.selector field is optional. In almost all cases you should not specify it.
  See section specifying your own pod selector.Parallel execution for JobsThere are three main types of task suitable to run as a Job:Non-parallel Jobsnormally, only one Pod is started, unless the Pod fails.the Job is complete as soon as its Pod terminates successfully.Parallel Jobs with a fixed completion count:specify a non-zero positive value for .spec.completions.the Job represents the overall task, and is complete when there are .spec.completions successful Pods.when using .spec.completionMode="Indexed", each Pod gets a different index in the range 0 to .spec.completions-1.Parallel Jobs with a work queue:do not specify .spec.completions, default to .spec.parallelism.the Pods must coordinate amongst themselves or an external service to determine
  what each should work on. For example, a Pod might fetch a batch of up to N items
  ```