-
Epic
-
Resolution: Done
-
Critical
-
None
-
Support Timezone for CronJobs
-
False
-
False
-
Green
-
To Do
-
Impediment
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Goal:
Allow users to set time zone on a per cronjob basis.
Problem:
Clusters across different environments have different timezones. There is no known recommendation or conformance test to define timezone for the control plane. Different distributions may have different behavior. For CronJob, the timezone is inferred from the control plane (specifically, the timezone as seen by the kube-controller-manager process). Someone with just API access has no idea what that controller manager timezone is. Sometimes cluster operators too, who run the controller manager in a container with a UTC timezone on a host with a non-UTC timezone.
Why is this important:
It is one of the most requested features by our customers according to PX Impact Score.
- relates to
-
RFE-1501 run cronjobs as per time zone set in Openshift nodes
-
- Accepted
-
1.
|
Docs Tracker |
|
Closed | |
Unassigned |
2.
|
QE Tracker |
|
Closed | |
Unassigned |
3.
|
TE Tracker |
|
Closed | |
Unassigned |