Kubernetes Ingress Generator
Build a networking.k8s.io/v1 Ingress from simple lines of host, path and service:port. Add ingress class, TLS, cert-manager issuer and common nginx annotations.
Use the tool
Why this tool exists
Ingress manifests look simple but have many details: the v1 API needs a pathType and a backend with a named service and port, TLS needs the host list and a secret, and every controller uses its own annotations. Older examples online still use v1beta1, which no longer works.
Write one rule per line, such as app.example.com /api api:8080 Prefix, and the tool groups rules by host, adds the TLS section when you give a secret name, and sets the ingress class. For the nginx class it can add the SSL redirect, a body size limit and a rewrite target, and for cert-manager the cluster issuer annotation. Annotations differ between controllers, so check the ones you use. Your input is not uploaded.
How to use it
- Write one rule per line: host, path, service:port and optionally Prefix, Exact or ImplementationSpecific.
- Enter the ingress name, namespace and ingressClassName.
- Add a TLS secret name and cert-manager issuer if you want HTTPS.
- Copy the YAML and apply it with kubectl.
Frequently asked questions
What path types are allowed?
Prefix, Exact and ImplementationSpecific. If you leave the type off, Prefix is used. The path must start with a slash.
How is TLS configured?
When you give a TLS secret name, all hosts in your rules are listed in one tls entry using that secret. With the cert-manager issuer set, cert-manager can create the certificate for you.
Are the annotations valid for every controller?
No. The nginx options only apply to the nginx ingress controller and are added only when the class is nginx. Other controllers use different annotations.
Do I need a Service already?
Yes. The Ingress points to Services by name and port. Create them first, for example with the Kubernetes Deployment Generator.