CronJobs (previously ScheduledJobs)

[soltysh]

Enhancement Description

• One-line feature description (can be used as a release note):
  CronJobs (previously ScheduledJobs) are meant for performing all time-related actions, namely backups, report generation and the like. Each of these tasks should be allowed to run repeatedly (once a day/month, etc.) or once at a given point in time.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/19-Graduate-CronJob-to-Stable
• Discussion Link: sig-apps agenda
• Primary contact (assignee): @soltysh
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target 1.4 (as ScheduledJobs)
  • Beta release target 1.8 (as CronJobs)
  • Stable API target 1.21
  • Stable controller target 1.22
    • switch storage to batch/v1 CronJob: switch storage version to batch/v1 in 1.22 kubernetes#102363
    • switch kubectl prune (and addon manager prune whitelist) to batch/v1 Clean apply's prune and kube addons with batch/v1 CronJob kubernetes#102528
    • kubectl sparse tests Promote cronjob to batch/v1: kubectl sparse_test file kubernetes#102338
    • switch kubectl create job owner ref to batch/v1 Drop beta APIs from create command for PDBs and CronJobs kubernetes#101613
    • switch controller to use batch/v1 Switch cronjob controller to batch/v1 kubernetes#99423
    • test fixes Promote cronjob integration test to batch/v1 kubernetes#102143
    • feature flag GA Promote CronJobControllerV2 flag to GA kubernetes#102529 & Promote CronJobControllerV2 flag to GA website#28229
    • various minor fixes fix: inaccurate miss schedule times of cronjob v2. kubernetes#101055
    • update cron library Update to github.com/robfig/cron/v3 kubernetes#102735
    • set lastSuccessfull populate last successful time to cronjob status kubernetes#102642
• Remove old controller target 1.23
  • Remove GAed feature gate CronJobControllerV2 kubernetes#104470

[soltysh]

@erictune fyi

[philips]

@soltysh On what SIG can I discuss this feature? I want to have a longer discussion about third-party resources for this feature and why we feel it needs to be built into core.

[erictune]

Let's use SIG-Apps for now. There has not been a lot of discussion of controllers there, that I have seen, but lets try and see how it goes.

[gtaylor]

Is this being considered for exclusion from the core? I had thought the proposal was already accepted.

[soltysh]

@gtaylor nothing has been decided yet. Currently it'll be part of alpha group in batch, what will happen when this migrates to more stable is not yet known.

[davidopp]

My understanding was that this was accepted into core, while job workflow was rejected for core. In fact we had originally planned to have it in 1.3.

[soltysh]

@davidopp my comment was based on the discussion we've previously had with @philips @erictune here. Although, personally I'd prefer SJ stay in the core 😎

[davidopp]

@soltysh I interpreted the comment as implying that it would be in core (based on the mention of alpha/beta and the statement "If someone were to produce a third-party version of scheduledJob, well before 1.4, and show that was comparably useful, that would be persuasive argument for the latter path" where the latter path was ThirdParty).

[erictune]

@davidopp that comment was made when I thought SJ would be Beta in 1.4. Now it is going to Alpha in 1.4. The philosophy was that we can cancel an alpha feature for whatever reason, but we should have a pretty high bar for cancelling a beta feature.

[erictune]

Also, to all working on SJ: we should continue work at full speed, despite the above conversation. Much of the work will apply either way, and we need to get some kind of feature out to users so they can give feedback.

[soltysh]

All SJ work is at full speed, the only remaining problem (hopefully) is to have kubernetes/kubernetes#29187 in. I'm hoping to discuss this issue with @smarterclayton today or over the weekend and have it merged so next week we should see one after the other SJ PRs being merged.