Kubernetes YAML Generator
Generate Kubernetes manifests — Deployment, Service, Ingress, ConfigMap, HPA, and more.
About Kubernetes YAML
Kubernetes uses YAML manifests to declare the desired state of resources in a cluster. This generator produces production-ready manifests following Kubernetes best practices: resource requests and limits to enable proper scheduling and prevent resource starvation, liveness and readiness probes to enable automatic restart of failed containers and prevent traffic to unready pods, security contexts to run containers as non-root with read-only root filesystems, and proper label selectors for service discovery.
FAQ
What is the difference between requests and limits?
Requests are what the container is guaranteed to receive — used by the scheduler to place pods on nodes with sufficient resources. Limits are the maximum the container can use — exceeding CPU limits causes throttling, exceeding memory limits causes OOMKill. Always set both for production workloads.
What is the difference between liveness and readiness probes?
Readiness probe: is the pod ready to receive traffic? Failing readiness removes the pod from the Service load balancer. Liveness probe: is the pod still alive and healthy? Failing liveness triggers a restart. Use readiness for warming up, liveness for detecting deadlocks.