instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from doing this.If you do end up with multiple controllers that have overlapping selectors, you
  will have to manage the deletion yourself (see below).Multiple ReplicasYou can specify how many pods should run concurrently by setting .spec.replicas to the number
  of pods you would like to have running concurrently. The number running at any time may be higher
  or lower, such as if the replicas were just increased or decreased, or if a pod is gracefully
  shutdown, and a replacement starts early.If you do not specify .spec.replicas, then it defaults to 1.Working with ReplicationControllersDeleting a ReplicationController and its PodsTo delete a ReplicationController and all its pods, use kubectl delete. Kubectl will scale the ReplicationController to zero and wait
  for it to delete each pod before deleting the ReplicationController itself. If this kubectl
  command is interrupted, it can be restarted.When using the REST API or client library, you need to do the steps explicitly (scale replicas to
  0, wait for pod deletions, then delete the ReplicationController).Deleting only a ReplicationControllerYou can delete a ReplicationController without affecting any of its pods.Using kubectl, specify the --cascade=orphan option to kubectl delete.When using the REST API or client library, you can delete the ReplicationController object.Once the original is deleted, you can create a new ReplicationController to replace it. As long
  as the old and new .spec.selector are the same, then the new one will adopt the old pods.
  However, it will not make any effort to make existing pods match a new, different pod template.
  To update pods to a new spec in a controlled way, use a rolling update.<h3 id=isolating-pods-
  ```