instruction: Create a Kubernetes Service configuration with best practices
output: ```dockerfile
  from server (NotFound): services "hostnames" not found
  Let's create the Service. As before, this is for the walk-through - you can
  use your own Service's details here.kubectl expose deployment hostnames --port=80 --target-port=9376
  service/hostnames exposed
  And read it back:kubectl get svc hostnames
  NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
  hostnames ClusterIP 10.0.1.175 <none> 80/TCP 5s
  Now you know that the Service exists.As before, this is the same as if you had started the Service with YAML:apiVersion: v1
  kind: Service
  metadata:
   labels:
   app: hostnames
   name: hostnames
  spec:
   selector:
   app: hostnames
   ports:
   - name: default
   protocol: TCP
   port: 80
   targetPort: 9376
  In order to highlight the full range of configuration, the Service you created
  here uses a different port number than the Pods. For many real-world
  Services, these values might be the same.Any Network Policy Ingress rules affecting the target Pods?If you have deployed any Network Policy Ingress rules which may affect incoming
  traffic to hostnames-* Pods, these need to be reviewed.Please refer to Network Policies for more details.Does the Service work by DNS name?One of the most common ways that clients consume a Service is through a DNS
  name.
  ```