Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-341

Support Timezone for CronJobs

    XMLWordPrintable

Details

    • Epic
    • Status: Dev Complete
    • Critical
    • Resolution: Unresolved
    • None
    • openshift-4.11
    • Support Timezone for CronJobs
    • False
    • False
    • Green
    • To Do
    • Impediment
    • 100
    • 100% 100%
    • Undefined

    Description

      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.

      Attachments

        Issue Links

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          QE Tracker Sub-task Closed Undefined Unassigned
          3.
          TE Tracker Sub-task Closed Undefined Unassigned

          Activity

            People

              maszulik1@redhat.com Maciej Szulik
              gausingh@redhat.com Gaurav Singh
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: