KA-R012: CronJob missing startingDeadlineSeconds

Warning Reliability

Why This Matters

The CronJob does not set startingDeadlineSeconds. Without a deadline, if the CronJob controller misses a schedule (e.g., due to controller downtime), it may create many jobs at once when it recovers, overwhelming the cluster.

How to Fix

Add startingDeadlineSeconds to the CronJob spec

Before (incorrect)

apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "*/5 * * * *"

After (correct)

apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "*/5 * * * *"
  startingDeadlineSeconds: 200

Rule Details

Rule Code: KA-R012
Severity: Warning
Category: Reliability

Related Rules

KA-R011 Error

Selector/template label mismatch

KA-R001 Warning

Missing liveness probe

KA-R002 Warning

Missing readiness probe

KA-R003 Warning

Identical liveness and readiness probes

KA-R004 Warning

Single replica Deployment