instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from the largest ordinal to the smallest), updating
  each Pod one at a time.The Kubernetes control plane waits until an updated Pod is Running and Ready prior
  to updating its predecessor. If you have set .spec.minReadySeconds (see
  Minimum Ready Seconds), the control plane additionally waits that
  amount of time after the Pod turns ready, before moving on.Partitioned rolling updatesThe RollingUpdate update strategy can be partitioned, by specifying a
  .spec.updateStrategy.rollingUpdate.partition. If a partition is specified, all Pods with an
  ordinal that is greater than or equal to the partition will be updated when the StatefulSet's
  .spec.template is updated. All Pods with an ordinal that is less than the partition will not
  be updated, and, even if they are deleted, they will be recreated at the previous version. If a
  StatefulSet's .spec.updateStrategy.rollingUpdate.partition is greater than its .spec.replicas,
  updates to its .spec.template will not be propagated to its Pods.
  In most cases you will not need to use a partition, but they are useful if you want to stage an
  update, roll out a canary, or perform a phased roll out.Maximum unavailable PodsFEATURE STATE:
  Kubernetes v1.24 [alpha]You can control the maximum number of Pods that can be unavailable during an update
  by specifying the .spec.updateStrategy.rollingUpdate.maxUnavailable field.
  The value can be an absolute number (for example, 5) or a percentage of desired
  Pods (for example, 10%). Absolute number is calculated
  ```