instruction: Create a Kubernetes configuration with Service, Pod resources
output: ```dockerfile
  from within
  the Pod).If there exists a headless Service in the same namespace as the Pod, with
  the same name as the subdomain, the cluster's DNS Server also returns A and/or AAAA
  records for the Pod's fully qualified hostname.Example:apiVersion: v1
  kind: Service
  metadata:
   name: busybox-subdomain
  spec:
   selector:
   name: busybox
   clusterIP: None
   ports:
   - name: foo # name is not required for single-port Services
   port: 1234
  ---
  apiVersion: v1
  kind: Pod
  metadata:
   name: busybox1
   labels:
   name: busybox
  spec:
   hostname: busybox-1
   subdomain: busybox-subdomain
   containers:
   - image: busybox:1.28
   command:
   - sleep
   - "3600"
   name: busybox
  ---
  apiVersion: v1
  kind: Pod
  metadata:
   name: busybox2
   labels:
   name: busybox
  spec:
   hostname: busybox-2
   subdomain: busybox-subdomain
   containers:
   - image: busybox:1.28
   command:
   - sleep
   - "3600"
   name: busybox
  Given the above Service "busybox-subdomain" and the Pods which set spec.subdomain
  to "busybox-subdomain", the first Pod will see its own FQDN as
  "busybox-1.busybox-subdomain.my-namespace.svc.cluster-domain.example". DNS serves
  A and/or AAAA records at that name, pointing to the Pod's IP. Both Pods "busybox1" and
  "busybox2" will have their own address records.An EndpointSlice can specify
  the DNS hostname for any endpoint addresses, along with its IP.Note:A and AAAA records are not created for Pod names since hostname is missing for the Pod.
  A Pod with no hostname but with subdomain will only create the
  A or AAAA record for the headless Service (busybox-subdomain.my-namespace.svc.cluster-domain.example),
  pointing to the Pods' IP addresses. Also, the Pod needs to be ready in order to have a
  record unless publishNotReadyAddresses=True is set on the Service.Pod's setHostnameAsFQDN fieldFEATURE STATE:
  Kubernetes v1.22 [stable]When a Pod is configured to have fully qualified domain name (FQDN), its
  hostname is the short hostname. For example, if you have a Pod with the fully
  qualified domain name busybox-1.busybox-subdomain.my-namespace.svc.cluster-domain.example,
  then by default the hostname command inside that Pod returns busybox-1 and the
  hostname --fqdn command returns the FQDN.When you set setHostnameAsFQDN: true in the Pod spec, the kubelet writes the Pod's FQDN
  into the hostname for that Pod's namespace. In this case, both hostname and hostname --fqdn
  return the Pod's FQDN.Note:In Linux, the hostname field of the kernel (the nodename field of struct utsname) is limited to 64 characters.If a Pod enables this feature and its FQDN is longer than 64 character, it will fail to start.
  The Pod will remain in Pending status (ContainerCreating as seen by kubectl) generating
  error events, such as Failed to construct FQDN
  ```