-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote CronJobTimeZone to stable #39835
Conversation
@@ -183,7 +181,7 @@ Specifying a timezone that way is **not officially supported** (and never has be | |||
|
|||
If you try to set a schedule that includes `TZ` or `CRON_TZ` timezone specification, | |||
Kubernetes reports a [warning](/blog/2020/09/03/warnings/) to the client. | |||
Future versions of Kubernetes might not implement that unofficial timezone mechanism at all. | |||
Future versions of Kubernetes will prevent setting the unofficial timezone mechanism entirely. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sftim in preparation to land kubernetes/kubernetes#116252 I've changed this wording to be stronger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few thoughts. Basically LGTM. The feature gates page fixes are particularly relevant IMO.
@@ -251,6 +249,9 @@ For a reference to old feature gates that are removed, please refer to | |||
| `CSIStorageCapacity` | `true` | Beta | 1.21 | 1.23 | | |||
| `CSIStorageCapacity` | `true` | GA | 1.24 | - | | |||
| `ConsistentHTTPGetHandlers` | `true` | GA | 1.25 | - | | |||
| `CronJobTimeZone` | `false` | Alpha | 1.24 | 1.24 | | |||
| `CronJobTimeZone` | `true` | Beta | 1.25 | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| `CronJobTimeZone` | `true` | Beta | 1.25 | | | |
| `CronJobTimeZone` | `true` | Beta | 1.25 | 1.26 | |
@@ -251,6 +249,9 @@ For a reference to old feature gates that are removed, please refer to | |||
| `CSIStorageCapacity` | `true` | Beta | 1.21 | 1.23 | | |||
| `CSIStorageCapacity` | `true` | GA | 1.24 | - | | |||
| `ConsistentHTTPGetHandlers` | `true` | GA | 1.25 | - | | |||
| `CronJobTimeZone` | `false` | Alpha | 1.24 | 1.24 | | |||
| `CronJobTimeZone` | `true` | Beta | 1.25 | | | |||
| `CronJobTimeZone` | `true` | GA | 1.247| - | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| `CronJobTimeZone` | `true` | GA | 1.247| - | | |
| `CronJobTimeZone` | `true` | GA | 1.27 | - | |
For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}} | ||
interprets schedules relative to its local time zone. | ||
|
||
{{< feature-state for_k8s_version="v1.25" state="beta" >}} | ||
{{< feature-state for_k8s_version="v1.27" state="stable" >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For stable, move the feature state shortcode just under the heading, and put the detail about CronJobs with no time zone specified into a note callout later on in the Time zones section.
Consider moving the caution callout about TZ
/ CRON_TZ
to be the first item in CronJob limitations, and if you want you can hyperlink to that from somewhere within the Time zones section. We're really framing that now as a shortcoming rather than anything close to a feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the feature state should be under the Time zones section and not under the CronJob main heading, right?
@sftim I hope I addressed all the comments as you wished, ptal |
Looks ready for tech review. |
/assign @atiratree |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
LGTM label has been added. Git tree hash: ef2c02c0e6500f2237577b4e871ef424aee634c7
|
Adds documentation for:
/assign @sftim