TimeZone support in CronJob

[soltysh]

TimeZone support in CronJob

• TimeZone support in CronJob
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md
• Discussion Link: https://docs.google.com/document/d/1LZLBGW2wRDwAfdBNHJjFfk9CFoyZPcIYGWU7R1PQ3ng/edit#heading=h.h9p5t69007xy
• Primary contact (assignee): @soltysh
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.24
  • Beta release target (x.y): 1.25
  • Stable release target (x.y): 1.27
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP 3140: TimeZone support in CronJob #3143
  • Code (k/k) update PR(s):
    • KEP 3140: TimeZone support for CronJob kubernetes#108032 (comment)
  • Docs (k/website) update PR(s):
    • Document timezone support for CronJob website#32577
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3140: TimeZone support in CronJob #3375
  • Code (k/k) update PR(s):
    • Promote CronJobTimeZone to beta kubernetes#111435
  • Docs (k/website) update(s):
    • Promote CronJobTimeZone to beta website#35400
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP 3140: Promote CronJob's TimeZone support to GA #3449
  • Code (k/k) update PR(s):
    • Promote CronJob TZ to GA kubernetes#115904
    • Forbid creating CronJob with TZ or CRON_TZ, but allow updates kubernetes#116252
  • Docs (k/website) update(s):
    • Promote CronJobTimeZone to stable website#39835
  • Blog (k/website) update(s):
    • WIP: CronJob TimeZone blog website#39837

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

[soltysh]

/sig apps

[Priyankasaggu11929]

Hello @soltysh 👋, 1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022.

For note, This enhancement is targeting for stage alpha for 1.24 (correct me, if otherwise)

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would just require having this KEP PR #3143 merged & that will mark all the above requirements.

At the moment, the status of this enhancement is marked as at-risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[soltysh]

@Priyankasaggu11929 #3143 just merged, so I hope that satisfies all the requirements for inclusion.

[rhockenbury]

Thanks! I've moved this to tracked. All set for enhancement freeze. 👍

[mehabhalodiya]

Hi @soltysh 👋🏻 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

[salaxander]

Hi @soltysh 👋

Checking in once more as we approach 1.24 code freeze at 01:00 UTC Wednesday 30th March 2022.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

It looks like we're waiting on this one to merge? -> kubernetes/kubernetes#108032

As always, we are here to help should questions come up.

Thanks!!

[soltysh]

It looks like we're waiting on this one to merge? -> kubernetes/kubernetes#108032

correct, that's the only one we need.