Surface next scheduled time in CronJob status

[vishals-3]

Enhancement Description

• One-line enhancement description (can be used as a release note): Surface the next time a CronJob is scheduled to create a Job via a new alpha CronJobStatus.nextScheduleTime field, gated by the CronJobsNextScheduleTime feature gate.
• Kubernetes Enhancement Proposal: KEP PR to be linked (draft in progress)
• Discussion Link: add the next run jobs time to CronJobStatus kubernetes#78564 (original feature request, open since 2019)
• Primary contact (assignee): @vishals-3
• Responsible SIGs: sig-apps
• PRs by stage and milestone:
  • Alpha - v1.xx
    • KEP (k/enhancements) update PR(s): to be linked
    • Code (k/k) update PR(s): Add nextScheduleTime to CronJob status (alpha) kubernetes#141428
    • Docs (k/website) update PR(s):

Summary

CronJob status exposes lastScheduleTime but not the next scheduled time. Users
must reimplement cron parsing and time-zone handling to answer "when does this run
next?". The CronJob controller already computes this value internally to schedule
its requeue; this enhancement surfaces it as a read-only status field behind an
alpha feature gate. Fixes the long-standing request in kubernetes/kubernetes#78564.

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[kubernetes-prow]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[vishals-3]

KEP PR opened: #6282