Kubernetes CronJob Generator

Free Kubernetes CronJob YAML generator. Build a complete batch/v1 CronJob manifest with schedule, concurrencyPolicy, history limits, and container spec — ready to apply with kubectl apply -f. Standard 5-field cron syntax, timezone set by the cluster's node timezone.

⚡ Schedule Presets

🔧 CronJob Builder

Minute

0-59

Hour

0-23

Day/Month

1-31

Month

1-12

Day/Week

0=Sun

0 2 * * *

✅ Runs at minute 0 at 2:00 AM

CronJob name

Namespace

Container image

Command

concurrencyPolicy

Success history

Fail history

📋 Generated Kubernetes YAML

CronJob manifest — kubectl apply -f cronjob.yaml

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-cronjob
  namespace: default
spec:
  schedule: "0 2 * * *"
  concurrencyPolicy: Forbid
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: my-cronjob
              image: busybox:1.35
              command:
                - /bin/sh
                - -c
                - echo "Running scheduled task"

Helm values snippet

# values.yaml for a Helm chart
cronJob:
  name: my-cronjob
  schedule: "0 2 * * *"
  image: busybox:1.35
  command: "echo "Running scheduled task""
  concurrencyPolicy: Forbid

⚙️ concurrencyPolicy Explained

Forbid

If the previous job is still running when the next one is due, skip the new one. Use for jobs that must not overlap (DB migrations, backups).

Allow

Multiple instances can run simultaneously. Fine for idempotent jobs with no state conflicts. Default in older Kubernetes versions.

Replace

Kill the currently running job and start a new one. Use when fresh data is more important than completing the previous run.

❓ Kubernetes CronJob FAQ

How do I create a Kubernetes CronJob?

Apply the generated YAML with: kubectl apply -f cronjob.yaml. Verify with: kubectl get cronjobs. View logs with: kubectl logs job/my-cronjob-<timestamp>.

What timezone does Kubernetes CronJob use?

By default, Kubernetes CronJobs use the timezone of the kube-controller-manager node. Kubernetes 1.27+ added a timeZone field in the CronJob spec. For older clusters, convert your times to the node timezone.

How do I suspend a Kubernetes CronJob?

Run: kubectl patch cronjob my-cronjob -p '{"spec":{"suspend":true}}'. Resume with false. This stops new jobs from being created but doesn't affect currently running jobs.

What is successfulJobsHistoryLimit?

This controls how many completed Job objects Kubernetes keeps. Default is 3. Set to 0 to delete completed jobs immediately. Keeping some is useful for debugging with kubectl logs.

How do I run a CronJob manually?

kubectl create job --from=cronjob/my-cronjob manual-run-1. This creates a one-off Job from the CronJob template immediately.