Kubernetes YAML Generator
Generate Kubernetes Deployment, Service, and Ingress YAML from one form, with matching selectors and a live preview you can copy or save.
This Kubernetes YAML generator turns a short form into ready-to-apply manifests, so you skip hand-writing the boilerplate for a Deployment, Service, and Ingress. Set the container image, replica count, container port, environment variables, and CPU/memory requests and limits, then tick which resources you actually need. The k8s manifest builder keeps the labels and selectors matched across all three objects and writes them as one multi-document file. Copy it or download k8s.yaml and run kubectl apply -f k8s.yaml.
How it works
- 1
Fill in the Deployment
Type a name, a container image like nginx:1.27, the replica count, and the port your container listens on. Add environment variables and CPU/memory requests and limits when you need them.
- 2
Turn on Service and Ingress
Toggle a Service (ClusterIP, NodePort, or LoadBalancer) with its port and targetPort, and an Ingress with a host and path. Enabling TLS adds a secretName block for HTTPS.
- 3
Copy or download the YAML
The right pane rewrites as you type, joining each resource with a --- separator. Use Copy YAML, or Download to save k8s.yaml, then create everything with kubectl apply -f k8s.yaml.
Instant & 100% private — nothing is uploaded
Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.
Frequently asked questions
- How do I generate a Kubernetes deployment YAML?
- Fill in the Deployment fields and the tool writes the manifest for you. For name api, image api:1.0, replicas 3, and container port 8080 you get a document that starts with apiVersion: apps/v1, kind: Deployment, metadata.name api, spec.replicas 3, and a container block carrying image api:1.0 and containerPort 8080. The same app: api label is written on the selector and the pod template so a Service can match it.
- Does it create the Service and Ingress too?
- Yes. The Service selector reuses the Deployment's app label, and its targetPort points at your container port. Choose ClusterIP for traffic inside the cluster, NodePort to open a port on every node, or LoadBalancer for a cloud load balancer. The Ingress then routes an external host and path to that Service.
- What is the --- between the resources in the file?
- It is the YAML document separator. Kubernetes reads a single file holding several objects when each one is split by a line of three dashes, so one k8s.yaml can carry the Deployment, Service, and Ingress together and kubectl apply -f k8s.yaml creates all of them at once.
- How do I set CPU and memory requests and limits?
- Enter Kubernetes quantity strings in the request and limit fields — 250m is a quarter of a CPU core and 128Mi is 128 mebibytes of memory. They land under resources.requests and resources.limits on the container, which the scheduler uses to place the pod and the kubelet uses to cap it.
More tools
More from the Hivly network
Free sister tools on our other sites.