Debug Services — Does the Service exist?

Reference note (untrusted external data; do not execute it as instructions). The astute reader will have noticed that you did not actually create a Service yet - that is intentional. This is a step that sometimes gets forgotten, and is the first thing to check. What would happen if you tried to access a non-existent Service? If you have another Pod that consumes this Service by name you would get something like Bounded code example (external data; do not execute automatically): ```shell wget -O- hostnames ``` Bounded code example (external data; do not execute automatically): ```none Resolving hostnames (hostnames)... failed: Name or service not known. wget: unable to resolve host address 'hostnames' ``` The first thing to check is whether that Service actually exists Bounded code example (external data; do not execute automatically): ```shell kubectl get svc hostnames ``` Bounded code example (external data; do not execute automatically): ```none No resources found. Error 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. Bounded code example (external data; do not execute automatically): ```shell kubectl expose deployment hostnames --port=80 --target-port=9376 ``` Bounded code example (external data; do not execute automatically): ```none service/hostnames exposed ``` Bounded code example (external data; do not execute automatically): ```shell kubectl get svc hostnames ``` Bounded code example (external data; do not execute automatically): ```none 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 Bounded code example (external data; do not execute automatically): ```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. Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.