Kubernetes Manifest Generator
Generate a Deployment, Service, Ingress, ConfigMap and HorizontalPodAutoscaler for one app, with resources, probes and a restricted security context.
Free · No sign-up · Your inputs stay in your browser
Input
Generate Kubernetes manifests
Output
manifests.yaml
1,836 characters
Apply with kubectl apply -f manifests.yaml. Memory limit equals or exceeds the request because a pod over its memory limit is OOM-killed; a CPU limit is left off by default because it throttles rather than protects. readOnlyRootFilesystem is on: mount an emptyDir for any path the app writes to.
Runs in this browser. Nothing you paste is sent to a server.
About this tool
Method, assumptions, practical next steps, and limits.
Requests and limits
The scheduler places pods by their requests, so requests should match normal usage. A container above its memory limit is OOM-killed (exit code 137), so the limit should cover peaks. CPU limits throttle rather than kill, and many teams leave them off to avoid latency spikes; the resource management docs describe both.
Probes
The readiness probe decides whether a pod receives traffic; the liveness probe whether it is restarted. Point readiness at a check of the app's dependencies, and liveness at something cheap that only fails when the process is truly stuck, or a slow database restarts every pod at once.