instruction: Create a Dockerfile for workloads
output: ```dockerfile
  from a deck of cards; each queue is a
  metaphorical card. The shuffle-sharding technique starts with hashing
  the flow-identifying characteristics of the request, to produce a hash
  value with dozens or more of bits. Then the hash value is used as a
  source of entropy to shuffle the deck and deal a hand of cards
  (queues). All the dealt queues are examined, and the request is put
  into one of the examined queues with the shortest length. With a
  modest hand size, it does not cost much to examine all the dealt cards
  and a given low-intensity flow has a good chance to dodge the effects of a
  given high-intensity flow. With a large hand size it is expensive to examine
  the dealt queues and more difficult for the low-intensity flows to dodge the
  collective effects of a set of high-intensity flows. Thus, the hand size
  should be chosen judiciously.Sidecar ContainerOne or more containers that are typically started before any app containers run.[+]Sidecar containers are like regular app containers, but with a different purpose: the sidecar provides a Pod-local service to the main app container.
  Unlike init containers, sidecar containers
  continue running after Pod startup.Read Sidecar containers for more information.SIG (special interest group)Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.[+]Members within a SIG have a shared interest in advancing a specific area, such as architecture, API machinery, or documentation.
  SIGs must follow the SIG governance guidelines, but can have their own contribution policy and channels of communication.For more information, see the kubernetes/community repo and the current list of SIGs and Working Groups.SpecDefines how each object, like Pods or Services, should be configured and its desired state.[+]Almost every Kubernetes object includes two nested object fields that govern the object's configuration: the object spec and the object status. For objects that have a spec, you have to set this when you create the object, providing a description of the characteristics you want the resource to have: its desired state.It varies for different objects like Pods, StatefulSets, and Services, detailing settings such as containers, volumes, replicas, ports,and other specifications unique to each object type. This field encapsulates what state Kubernetes should maintain for the definedobject.StatefulSetManages the deployment and scaling of a set of Pods, and provides guarantees about the ordering and uniqueness of these Pods.[+]Like a Deployment, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of its Pods. These pods are created
  ```