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
WIP: Add cronjob timezone #102889
WIP: Add cronjob timezone #102889
Conversation
@iterion: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
Hi @iterion. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
/remove-sig api-machinery |
pkg/apis/batch/types.go
Outdated
// The time zone to be used when scheduling the job given the schedule specified above. | ||
// Valid options include anything in the IANA Time Zone database. | ||
// +optional | ||
TimeZone string |
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.
should be *string
for it to be optional
// The time zone to be used when scheduling the job given the schedule specified above. | ||
// Valid options include anything in the IANA Time Zone database. | ||
// +optional | ||
TimeZone string `json:"timeZone,omitempty" protobuf:"bytes,8,opt,name=timeZone"` |
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.
same
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: iterion The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/remove-sig api-machinery |
/hold |
It seems like the ask has been satisfied, but maybe we need clearer criteria? How do we move this forward? I'm happy to help out with a KEP, and to advocate for this, but I'm not sure where to start. |
@iterion: PR needs rebase. 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/test-infra repository. |
Start with presenting the idea to sig-apps at one of our next meetings. We can make the initial decision there and we can get the final approval from sig-architecture after that. If you're willing to write down the KEP we can easily plan this for 1.23. |
Feel free to ping me on slack and I can get you pointed and setup where needed. |
@iterion do you think you could make the next sig-apps call on July 26th to talk about this? |
@soltysh sorry for the delay. I should be able to make it on July 26, what time does the meeting happen? My calendar is open for much of the day. |
@iterion it's 9am pacific |
Cool, I'm available to attend. |
@iterion Thank you so much. Most of k8s users are waiting this feature, thanks again caring about us ! |
Hello, the current cronjob already supports timezone handling. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/close |
@dims: Closed this PR. In response to this:
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/test-infra repository. |
please reopen if you still need this WIP PR. Trying to declutter the open PR(s) |
The previous method using See #104404 |
See #47202 |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
This PR adds a new field to the
CronJobSpec
namedTimeZone
that allows users to choose the specific time zone to use when scheduling jobs. If not specified, the previous default behavior of using the local time for thekube-controller-manager
is preserved.The ability to specify time zones is useful for Kubernetes users in situations where application requirements necessitate running jobs in specific time zones. In situations where users don't have control over the control plane local time, this also allows users to choose a time zone that is consistent and known to them.
Which issue(s) this PR fixes:
Fixes #47202
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: