Kubernetes Manifest Builder

Turn a short description of your apps into ready-to-apply Kubernetes YAML, checked for common mistakes.

Private by design

Your inputs stay on your device and are not sent to our servers. Optional usage analytics does not receive your files or tool inputs.

Kubernetes Manifest Builder

Apps in, Deployment, Service, Ingress and ConfigMap YAML out

Apps, one per line

YAML

The result appears here.

Options

Namespace (optional)

Service type

Ingress class (optional)

Add TLS to Ingress (secret named <app>-tls)

Add health probes

Uses health= if set, otherwise a TCP check on the port.

Add resource requests and a memory limit

Run as non-root, read-only filesystem

Turn off if your image needs to write files or run as root.

A Deployment runs your containers, a Service gives them a stable address, an Ingress sends outside web traffic to a Service, and a ConfigMap holds settings. Write one line per app and the matching YAML is built for you.

Pin image versions instead of :latest so deploys are repeatable.
Use 2 or more replicas for anything users depend on.
Preview with kubectl apply --dry-run=server -f manifests.yaml before applying.

Generated from the apps/v1, v1 and networking.k8s.io/v1 APIs. Names follow DNS-1123 label rules, labels use app.kubernetes.io/name, and the Service selects the same label as the Deployment. Runs in your browser; no cluster is contacted.

Preparing tool

How to use Kubernetes Manifest Builder

Write one line per app: its name, then image=, port=, replicas=, host= and any env.NAME= or config.NAME= values.
Choose the namespace, service type, health checks, resource requests and security defaults.
Fix anything in the checks, then copy or download the YAML and run kubectl apply -f.

Read the detailed guide →

What are the limits of Kubernetes Manifest Builder?

Builds Deployment, Service, Ingress and ConfigMap only: no Secrets, volumes, autoscaling, jobs or StatefulSets. Checks names, ports, images, quantities and hosts against Kubernetes rules but does not talk to a cluster, so a cluster may still reject a manifest (for example a missing ingress class). Do not put real secrets in the input. Your text stays on your device.