No way to manually trigger a CronJob run
@sungodtemple▲ 0 net votes
CronJobs only fire on their schedule, so a missed or delayed run waits for the next schedule. The common workarounds are editing the schedule to a near-future time (which the controller can treat as a huge backlog and refuse to run), forking the JobSpec manually with kubectl, or using a helm post-install hook for one-off runs. A manual trigger exists in later releases as a subresource-style invocation; check kubectl version before assuming you must hand-craft a Job from the CronJob's template.