instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from doing this.If you have multiple controllers that have overlapping selectors, the controllers will fight with each
  other and won't behave correctly.Strategy.spec.strategy specifies the strategy used to replace old Pods by new ones.
  .spec.strategy.type can be "Recreate" or "RollingUpdate". "RollingUpdate" is
  the default value.Recreate DeploymentAll existing Pods are killed before new ones are created when .spec.strategy.type==Recreate.Note:This will only guarantee Pod termination previous to creation for upgrades. If you upgrade a Deployment, all Pods
  of the old revision will be terminated immediately. Successful removal is awaited before any Pod of the new
  revision is created. If you manually delete a Pod, the lifecycle is controlled by the ReplicaSet and the
  replacement will be created immediately (even if the old Pod is still in a Terminating state). If you need an
  "at most" guarantee for your Pods, you should consider using a
  StatefulSet.Rolling Update DeploymentThe Deployment updates Pods in a rolling update
  fashion when .spec.strategy.type==RollingUpdate. You can specify maxUnavailable and maxSurge to control
  the rolling update process.Max Unavailable.spec.strategy.rollingUpdate.maxUnavailable is an optional field that specifies the maximum number
  of Pods that can be unavailable during the update process. The value can be an absolute number (for example, 5)
  or a percentage of desired Pods (for example, 10%). The absolute number is calculated
  ```