☸️ Kubernetes YAML Generator
Generate Kubernetes Deployment, Service, and Ingress YAML manifests from a form with sensible defaults.
# Generated YAML will appear here…
About this tool
The Kubernetes YAML Generator helps you scaffold Deployment, Service, and Ingress manifests without looking up the API reference for every field. Pick a resource type, fill in the form fields, and get a ready-to-apply YAML with production-ready defaults — resource limits, health probes, rolling updates, and TLS support for Ingress.
Example: select Deployment, set image to nginx:1.27, replicas to 3, add a container port 80/HTTP, and enable liveness + readiness probes — you get a complete Deployment YAML with resource requests/limits, health checks, and a rolling update strategy.
For a full microservice setup: generate a Deployment for your app, then switch to Service (same name, same labels) to expose it within the cluster, and finally an Ingress to route external traffic with a domain name and optional TLS.
FAQ
What Kubernetes API versions does this generator use? ›
Deployments use <code>apps/v1</code>, Services use <code>v1</code>, and Ingresses use <code>networking.k8s.io/v1</code> — the stable API versions supported by Kubernetes 1.19 and later.
Are the generated YAML files ready to apply with kubectl? ›
Yes — they follow the standard Kubernetes schema and include sensible defaults for common production scenarios. Review the image, resource limits, and probe paths for your specific application before applying.
How do I connect a Service to a Deployment? ›
Use the same labels on both resources. The Service <code>selector</code> and the Deployment <code>template.metadata.labels</code> must match. This generator uses a shared labels form for all resource types so they stay in sync.
Can I generate multiple resources at once? ›
This generator creates one resource at a time. To combine a Deployment, Service, and Ingress into a single file, generate each one separately, then concatenate them with <code>---</code> YAML document separators between each resource.