Port Mapping Formatter

Services route traffic to pods by mapping a Service port to a container targetPort. The Port Mapping Formatter writes a valid Service (v1) and documents each mapping so you can see port -> targetPort at a glance.

You set the Service name, type and selector, then add port rows. Each row has a name, protocol, port, targetPort and an optional nodePort (for NodePort/LoadBalancer). The output is a valid core/v1 Service with a reference header.

Names are validated as RFC 1123 labels. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.

• Service v1 - correct Service schema.
• port -> targetPort - clear mapping reference.
• Named targetPort - numeric or named containerPort.
• nodePort - optional for NodePort/LoAdBalancer.
• Validation - RFC 1123 names and required fields.
• Copy / Download / Print - get service.yaml wherever you need it.

1. Name the Service and pick a type.
2. Add a selector so the Service finds pods.
3. Add port rows (port, targetPort, protocol, nodePort).
4. Watch the preview and export.

Example 1 - simple. port 80 -> targetPort 8080 (TCP).

Example 2 - named. targetPort http (named containerPort).

Example 3 - NodePort. nodePort 30080.

• Correct schema - valid core/v1 Service.
• Clear mapping - port -> targetPort documented.
• Validated - names and required fields checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.