Dev
Kubernetes Manifest Prompt Generator
Writing a Kubernetes manifest from scratch invites the kinds of mistakes kubectl rejects — mismatched selector labels, a missing probe, or wrong API version. This tool generates a fill-in prompt you hand to an AI assistant so it writes a manifest that actually applies cleanly. Pick the resource kind — Deployment, StatefulSet, CronJob, or Ingress — and enter your app name (sanitised to kebab-case). The prompt pins the API version and kind, demands matching labels across selector, pod template, and Service, asks for CPU and memory requests and limits, readiness and liveness probes, and a namespace and replica count where applicable. Replace angle-bracket placeholders like `<registry>`, `<tag>`, and `<namespace>` before sending, then validate with `kubectl apply --dry-run=client -f`.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Pick the Kubernetes resource kind.
- Enter your app name.
- Click Generate to build the prompt.
- Replace the placeholders and paste it into your AI assistant.
Use Cases
- •Getting a consistent Kubernetes manifest from an AI assistant
- •Avoiding selector and label mismatches in generated YAML
- •Standardising how a team asks for infrastructure manifests
- •Scaffolding a StatefulSet or CronJob without memorising fields
- •Teaching teammates what a complete manifest request needs
Tips
- →Fill in the namespace and port before sending for a tighter result.
- →Ask the model to add probes — they are easy to forget.
- →Request a trailing comment on any field you do not recognise.
- →Run kubectl apply --dry-run=client to validate the output.
FAQ
why generate a prompt rather than the YAML directly
The prompt lets an AI assistant fill in your real stack specifics — registry, port, namespace, replica count — while the structured requirements ensure it includes probes, resource limits, and correctly matched labels that a bare template would omit.
what do the angle-bracket placeholders mean
Tokens like <registry>, <tag>, <port>, and <namespace> mark values only you know. Replace them before sending the prompt so the assistant produces a manifest with your real image path and configuration rather than generic placeholders.
does it support resource kinds beyond the four listed
No. The generator covers Deployment, StatefulSet, CronJob, and Ingress. Any input outside those four defaults to Deployment. For other kinds such as DaemonSet or Service, adapt the generated prompt by editing the kind line manually.
why does the prompt omit replicas for CronJob and Ingress
CronJobs manage their own pod lifecycle per schedule and have no replica count; Ingress is a routing rule, not a workload. The replica requirement is included only for Deployment and StatefulSet where it is meaningful.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.