Ingress Path Rule Builder

Ingress exposes HTTP/HTTPS routes from outside the cluster to services. The Ingress Path Rule Builder writes a networking.k8s.io/v1 Ingress with multiple path rules so you do not have to recall the schema.

You set the Ingress name, namespace, host and ingressClassName, then add paths. Each path has a path, a pathType (Prefix/Exact/ImplementationSpecific) and a service backend (name + port). The resulting YAML is valid networking.k8s.io/v1.

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

• networking.k8s.io/v1 - correct Ingress schema.
• Multiple paths - any number of HTTP rules.
• pathTypes - Prefix, Exact, ImplementationSpecific.
• Backends - service name + port.
• Validation - RFC 1123 names and required fields.
• Copy / Download / Print - get ingress.yaml wherever you need it.

1. Name the Ingress and host.
2. Add paths with pathType and a service backend.
3. Watch the preview and export.

Example 1 - Prefix. /api -> svc-api:8080.

Example 2 - Exact. /healthz -> svc-web:80.

Example 3 - ImplementationSpecific. / -> svc-web:80.

• Correct schema - valid networking.k8s.io/v1 Ingress.
• Flexible - any combination of paths.
• 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.