Cron Doctor · configuration analysis

Kubernetes CronJob validator

Inspect one CronJob with its Job template. Timing and controller settings affect different parts of the scheduled workload.

Open Cron Doctor

What you can check

Use an explicit spec.timeZone when timezone must be established from the manifest.
Review concurrencyPolicy and suspension settings.
Inspect activeDeadlineSeconds and backoffLimit when supplied.

What remains unknown

Checks cover selected batch/v1 fields. Missing timezone or an unsupported API version limits coverage; analyze multiple CronJobs one at a time. Static checks do not observe the cluster.

Synthetic example

apiVersion: batch/v1
kind: CronJob
metadata:
  name: backup
spec:
  schedule: '0 2 * * *'
  timeZone: UTC
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: backup
              image: busybox:1.36
              command: [echo, ok]
          restartPolicy: Never

Your configuration is sent to PingCron for analysis. It is not saved and is never executed. A static report does not establish runtime health.

Official scheduler reference · Explore ongoing monitoring