Ingress YAML Generator

An Ingress is how you expose HTTP and HTTPS services to the outside world without a separate load balancer per service. It defines rules that map hostnames and URL paths to backend Services inside the cluster, and it is the standard, controller-agnostic way to route external traffic. The Ingress YAML Generator builds that manifest from a form so you do not have to recall the networking.k8s.io/v1 schema.

You set the Ingress name and, optionally, a namespace, top-level labels and an ingressClassName that selects the controller. Then you add rules: each rule has a host (or a blank host to match any) and one or more paths. For each path you choose a path, a pathType - Prefix, Exact or ImplementationSpecific - and the backend Service name and port. Numeric ports stay numbers; named ports stay strings.

Optionally you add a TLS block per host list, referencing a Secret that holds the certificate. The form keeps TLS, rules and paths in clearly separated, repeatable sections so multi-host and multi-path configurations are easy to assemble. The name is validated as an RFC 1123 label and at least one path with a backend Service is required before any YAML is produced.

The live preview updates as you type and a small statistics strip shows the number of rules and paths. You can copy the manifest, download it as ingress.yaml, or print it. Everything runs locally and nothing is uploaded.

• Rules and paths - add as many hosts and paths as you need.
• pathType support - Prefix, Exact or ImplementationSpecific.
• Backend services - Service name plus numeric or named port.
• TLS blocks - hosts plus a certificate Secret name.
• ingressClassName - optional controller selection.
• Labels - optional metadata labels.
• Validation - RFC 1123 name and at least one backend path required.
• Copy / Download / Print - get ingress.yaml wherever you need it.

1. Name the Ingress. Type a valid RFC 1123 name and, optionally, a namespace.
2. Set ingressClassName (optional) to pick a controller.
3. Add TLS (optional): hosts and certificate Secret name.
4. Add rules. For each, set a host and one or more paths.
5. Set each path. Choose path, pathType, backend Service and port.
6. Watch the preview. The Ingress YAML appears on the right.
7. Export. Copy, download ingress.yaml, or print.

Example 1 - Single path. Host example.com, path / routed Prefix to service web on port 80.

Example 2 - Multiple paths. /api to api:8080 and / to web:80.

Example 3 - TLS. TLS hosts example.com with secret tls-secret.

Example 4 - Named port. Backend port http (named) instead of a number.

Example 5 - Blank host. A rule with no host matches all hosts.

• Correct schema - valid networking.k8s.io/v1 output.
• Multi-host ready - many rules and paths.
• Flexible backends - numeric or named ports.
• TLS aware - certificate Secret references.
• Validated - names and required backends checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.