Pods come and go, and each new one gets a new IP address, so nothing should call a Pod directly. A Service gives a set of Pods one stable name and virtual IP. It picks its Pods with a label selector and spreads traffic across the Ready ones; the current list of Pod addresses is its endpoints.
Every Service port has two numbers. port is what clients call; targetPort is where the containers listen. They are often different, for example 80 outside and 8080 inside, and if you leave targetPort out it copies port.
kubectl expose deployment NAME --port=80 --target-port=8080 creates a ClusterIP Service with the Deployment's selector. To test one, run a throwaway Pod in the same namespace and call the Service by name. The response comes from whichever Ready Pod the Service picked.
Create, check endpoints, call it from inside.