A ClusterIP Service, the default, is reachable only inside the cluster. Two other types open it up. A NodePort Service opens the same port, from 30000 to 32767, on every node and forwards it to the Service; you can pick the number with nodePort or let the cluster choose. A LoadBalancer Service does that and also asks the cloud provider for an external load balancer, whose address appears in the EXTERNAL-IP column once it exists.
For web traffic with host names and paths, teams usually put an Ingress or a Gateway in front instead, which you will meet at the Advanced level.
When you only need to look at a Service yourself, don't expose it at all: kubectl port-forward service/NAME 8080:80 tunnels a local port to it through the API server. The order is LOCAL:REMOTE, and the remote side is the Service's port.
Open it on the nodes, or tunnel to it from your machine.