/sig apps

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!

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

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

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!

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!!

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

correct, that's the only one we need.

docs placeholder opened in kubernetes/website#32577

When we document this, #3143 (comment) strongly suggests to me that we should document how to manage a custom timezone database (via a hostPath volume mount or similar), and we should do that unless we have a strong commitment from SIG Release about providing official container images for the controller manager that have the timezone data kept very current.

@soltysh Hi! Have you been working on this? If not, I am interested in this feature and I would like to implement it!

@knight42 this merged as alpha in 1.24 see kubernetes/kubernetes#108032 and kubernetes/website#32577 We're planning to promote this further in the next releases.

/milestone clear
/tracked no

/milestone v1.25
/stage beta

With #3449 merged this enhancement will be tracked for v1.27
Thanks!

The implementation of the CronJob API in Kubernetes 1.26 lets you set the .spec.schedule field to include a timezone; for example: CRON_TZ=UTC * * * * * or TZ=UTC * * * * *.

Do we want to make a stronger statement about this, now that we nearly have GA support for setting a timezone via the API? The other mechanism was never official. This feels like the right time to make it.

For example, we might want to block creates of CronJobs that set a schedule with TZ / CRON_TZ. Possibly behind an on-y-default, disable-if-you-must feature gate?

Do we want to make a stronger statement about this, now that we nearly have GA support for setting a timezone via the API? The other mechanism was never official. This feels like the right time to make it.

I'd wish, but my worry is that we might break users, I'll open a separate PR and let's see if api approvers are willing to accept that.

For example, we might want to block creates of CronJobs that set a schedule with TZ / CRON_TZ. Possibly behind an on-y-default, disable-if-you-must feature gate?

We would need to touch both creates, to ensure new cronjobs are w/o those, and also updates such that you can't add it, if it wasn't already there.

I guess, related thing: recommend a tool / script / whatever that converts to the new, GA way to use a timezone.

I guess, related thing: recommend a tool / script / whatever that converts to the new, GA way to use a timezone.

I'll be writing a blog post about the TZ GA, so I'll make sure to put something together, I think a simple one-liner that could handle that easily. Also, based on the discussion from the TZ/CRON_TZ PR (not opened yet) I'll add that information to that blog post as well.

@soltysh I wonder if, in your blog post, you'd be able to touch upon a recommended migration path for users who are on e.g. v1.22 and cronjobber.hidde.co/v1alpha1/TZCronJob. I am not sure in which point release we should attempt switching or even if we should temporarily use this TZ/CRON_TZ schedule format. Also we are constrained by the default feature gates, if that makes any difference.

Good point, I'll have a look and see what's possible.

Hi @soltysh, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

Hi @soltysh 👋,
Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.
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.
  • Promote CronJob TZ to GA kubernetes#115904

Please let me know what other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

Is there a way to see the timezone with kubectl ?
I don't see it today, even with kubectl get cronjobs -o wide.
My client is v1.27.2 although my server is only v1.26.10.
(I do see it with -o yaml or -o json but not in the tabular formats)

@dlipofsky as far as I understand the -o switch is pretty flexible and you can format it the way you want with it. Try go-template mode for example, I'm pretty sure it will get you where you want, I'm a little bit less certain about custom-columns but seems plausible too.

@AndrewSav, I was rather hoping it could be added as a standard feature, as it is just as important as the schedule string in knowing when something will actually run.

@dlipofsky let's hope they add it, but it is understandable that they cannot add every single field someone finds useful

For showing timezone in kubectl for CronJobs: https://github.com/kubernetes/kubectl/issues/new/choose

This is all done
/close

@soltysh: Closing this issue.