Yoryantra
Home/Tools
← Back to Tools

Kubernetes Service Port Mapper

Map Kubernetes Service ports from pasted YAML. Review service type, port, targetPort, nodePort, selectors, container ports, ingress hosts, and exposure notes.

Paste Service, Deployment, Pod, and Ingress YAML to map ports and exposure.

Mapping Settings

Port fields

porttargetPortnodePortcontainerPorthost

Checks

This mapper reads pasted YAML only. It does not contact a Kubernetes cluster or check live endpoints.

Output

Kubernetes service port mapping output will appear here.
This tool analyzes pasted Kubernetes YAML locally in your browser. It does not contact a cluster, test endpoints, or verify live service routing.

Mapping Kubernetes Service Ports Before Deployment

Kubernetes Service YAML can be confusing because a service port, targetPort, nodePort, and containerPort each mean something different. When manifests grow across Services, Deployments, and Ingress resources, mapping the traffic path helps avoid broken routing.

This Kubernetes Service Port Mapper extracts Service ports, target ports, node ports, selectors, container ports, and ingress hosts from pasted YAML so you can review exposure and routing in one place.

Using the Kubernetes Service Port Mapper

  1. Paste Kubernetes Service, Deployment, Pod, and Ingress YAML.
  2. Choose the output format and exposure filter.
  3. Review service type, selector, port, targetPort, nodePort, and containerPort values.
  4. Check warnings about exposure, missing target ports, or selector mismatches.
  5. Copy the summary, mapping, JSON, Markdown, CSV, or checklist output.

Service Port, TargetPort, and NodePort

  • port is the port exposed by the Kubernetes Service inside the cluster.
  • targetPort points to the container port or named port behind the service.
  • nodePort exposes the service on each node when the service type is NodePort.
  • containerPort documents which port the container process listens on.
  • Ingress hosts can route external HTTP traffic to a service and service port.

Example Service Mapping

Service web-service
type: NodePort
port: 80
targetPort: 8080
nodePort: 30080
selector: app=web

Selectors Decide Which Pods Receive Traffic

A Service does not send traffic to a Deployment directly. It selects Pods by labels. If the service selector does not match the Pod template labels, the service may exist but have no useful endpoints.

Use this mapper as a quick review helper, then confirm live routing with kubectl, endpoints, logs, and cluster-aware tests.

Frequently Asked Questions

What does a Kubernetes Service Port Mapper do?

It extracts Service ports, target ports, node ports, selectors, container ports, and ingress hosts from pasted Kubernetes YAML.

Does this contact my Kubernetes cluster?

No. It only analyzes pasted YAML locally in your browser.

What is the difference between port and targetPort?

port is the Service port. targetPort is the backend container port or named port that receives the traffic.

Can it detect selector mismatches?

It can compare simple Service selectors with labels found in workload manifests, but it is not a full cluster-aware endpoint checker.

Is anything uploaded when I map service ports?

No. The mapping runs directly in your browser.