instruction: Create a Kubernetes Pod configuration with best practices
output: ```dockerfile
  from the Kubernetes
  environment. All DNS settings are supposed to be provided using the
  dnsConfig field in the Pod Spec.
  See Pod's DNS config subsection below.
  
  Note:"Default" is not the default DNS policy. If dnsPolicy is not
  explicitly specified, then "ClusterFirst" is used.
  The example below shows a Pod with its DNS policy set to
  "ClusterFirstWithHostNet" because it has hostNetwork set to true.
  apiVersion: v1
  kind: Pod
  metadata:
   name: busybox
   namespace: default
  spec:
   containers:
   - image: busybox:1.28
   command:
   - sleep
   - "3600"
   imagePullPolicy: IfNotPresent
   name: busybox
   restartPolicy: Always
   hostNetwork: true
   dnsPolicy: ClusterFirstWithHostNet
  Pod's DNS Config
  
  FEATURE STATE: Kubernetes v1.14 [stable]
  
  Pod's DNS Config allows users more control on the DNS settings for a Pod.
  The dnsConfig field is optional and it can work with any dnsPolicy settings.
  However, when a Pod's dnsPolicy is set to "None", the dnsConfig field has
  to be specified.
  Below are the properties a user can specify in the dnsConfig field:
  
  nameservers: a list of IP addresses that will be used as DNS servers for the
  Pod. There can be at most 3 IP addresses specified. When the Pod's dnsPolicy
  is set to "None", the list must contain at least one IP address, otherwise
  this property is optional.
  The servers listed will be combined to the base nameservers generated
  ```