Kubernetes CronJob Monitoring

Kubernetes runs your CronJob, but it will happily keep scheduling even when the business logic inside always fails. Ping CronCraft from the container when the work succeeds.

Teams comparing platforms often look at Cronitor too — see CronCraft vs Cronitor.

Example job snippet

# Simplified: run script then ping
apiVersion: batch/v1
kind: CronJob
metadata:
  name: nightly-report
spec:
  schedule: "0 7 * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: worker
            image: your-image:tag
            command:
            - /bin/sh
            - -c
            - |
              ./run_report.sh && curl -fsS https://croncraft.app/ping/YOUR_TOKEN > /dev/null
          restartPolicy: OnFailure

Use Kubernetes Secrets for the token rather than hardcoding it in a manifest.

Create job