Study. uk . com
  1. Home
  2. All questions
  3. Question 659

CKA study material · question 659 of 1000

A CronJob scheduled for 0 3 * * * fires at an unexpected wall-clock time after the control plane is moved to different hosts. What is the likely cause?

  1. The schedule was interpreted in the kube-controller-manager's local time zone
  2. Cron expressions are always evaluated in UTC regardless of configuration
  3. startingDeadlineSeconds shifted the run
  4. The CronJob controller rounds schedules to the nearest hour
Show the answer

Answer: A. The schedule was interpreted in the kube-controller-manager's local time zone

A CronJob with no timeZone is read in the controller manager's own local zone, so moving the control plane can move the effective time; setting timeZone makes it explicit.

Source: CronJob (Kubernetes) — Time zones

Challenge yourself on this topic → Study as cards