Generate Kubernetes Deployment and Service YAML — replicas, images, ports and resource limits.
How to use this tool
App name becomes the Deployment, Service and label name; image is the container image.
Replicas scale the pods; port is both the container port and the Service port.
One KEY=value per line, or leave blank for none.
Download as deployment.yaml and run kubectl apply -f deployment.yaml.
Formula & worked example
App my-app, image nginx:latest, 2 replicas, port 80 gives a Deployment with replicas: 2 and containerPort: 80, plus a ClusterIP Service on port 80, separated by —.
Limitations — read this before you rely on it
Starter manifests only: no resource requests/limits, probes, volumes, ConfigMaps/Secrets, ingress, autoscaling or namespaces. Secrets must never be written as plain env values — use a Secret object and envFrom/valueFrom in production.
Frequently asked questions
Save the output as a .yaml file and run kubectl apply -f <file> against a cluster you control.
It is a starter manifest. Add resource limits, probes, and proper secret handling before production use.
ClusterIP (internal only), NodePort and LoadBalancer. Ingress is not generated.
Not in this version — add volumeMounts, livenessProbe and readinessProbe to the YAML by hand.
Never as plain env values. Create a Kubernetes Secret and reference it with valueFrom or envFrom.