Job YAML Generator

A Job runs pods to completion and is the right choice for batch work: database migrations, data imports, report generation, one-off scripts. Unlike a Deployment it is not meant to stay running forever. The Job YAML Generator writes that manifest from a form so you do not have to recall the batch/v1 schema.

You set the Job name and, optionally, a namespace and labels. Then you configure how it runs: completions (how many pods must succeed), parallelism (how many run concurrently), backoffLimit (retries before failure) and optional activeDeadlineSeconds and ttlSecondsAfterFinished. The pod template requires a restartPolicy - OnFailure or Never - and you add containers with a name, image, optional command/args and environment variables.

The name is validated as an RFC 1123 label, at least one container with a name and image is required, and numeric fields must be non-negative integers. Problems are reported in a clear panel. Everything runs locally and nothing is uploaded.

• completions / parallelism - control how many pods run and succeed.
• backoffLimit - retries before the Job fails.
• Deadline and TTL - optional activeDeadlineSeconds and ttlSecondsAfterFinished.
• restartPolicy - OnFailure or Never, as required by Jobs.
• Containers - name, image, command/args and env.
• Validation - RFC 1123 name and required fields.
• Copy / Download / Print - get job.yaml wherever you need it.

1. Name the Job. Type a valid RFC 1123 name and, optionally, a namespace.
2. Set run parameters. completions, parallelism, backoffLimit, deadline, TTL.
3. Pick restartPolicy. OnFailure or Never.
4. Add containers. Name, image, command/args and env.
5. Watch the preview. The Job YAML appears on the right.
6. Export. Copy, download job.yaml, or print.

Example 1 - Single run. completions 1, parallelism 1, backoffLimit 3, restartPolicy OnFailure.

Example 2 - Command. A container with command /bin/sh and args -c,echo hi.

Example 3 - Env. Lines MODE=once become env entries.

Example 4 - Parallel. parallelism 4 runs four pods at once.

Example 5 - TTL. ttlSecondsAfterFinished 3600 cleans up finished Jobs.

• No schema guesswork - valid batch/v1 output.
• Correct run semantics - completions, parallelism, restartPolicy wired in.
• Multi-container ready - add as many containers as needed.
• Validated - names and required fields checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.