`````` According to <https github com rancher sandbox ranche rancher-users #rancher-desktop

Title

alert-salesmen-99581

08/12/2022, 7:08 PM

```
According to  <https://github.com/rancher-sandbox/rancher-desktop/issues/578#issuecomment-996557436>, I could add an overrides at `~/Library/Application\ Support/rancher-desktop/lima/_config/override.yaml` as follows, but it hasn't applied...

```# <https://github.com/rancher-sandbox/rancher-desktop/issues/578#issuecomment-996557436>
env:
  K3S_EXEC: --feature-gates=CronJobTimeZone=true

I just found the rancher logs

k3s.log

and it pointed out an error on the parameter... the correct is

env:
    K3S_EXEC: --kube-apiserver-arg --feature-gates=CronJobTimeZone=true

I can see now under

k3s.log

the api server with the parameter

time="2022-08-12T19:15:59Z" level=info msg="Running kube-apiserver --advertise-address=192.168.86.249 --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=<https://kubernetes.default.svc.cluster.local>,k3s --authorization-mode=Node,RBAC --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --etcd-servers=<unix://kine.sock> --feature-gates=CronJobTimeZone=true --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --profiling=false --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=<https://kubernetes.default.svc.cluster.local> --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"

After that, I can see now the timezone being validated when attempting to apply

persistentvolumeclaim/timecard-persistent-volume-claim-local-localhost-prdt-ppd-loc unchanged
The CronJob "timecard-cron-job-local-localhost-prdt-ppd-loc" is invalid: spec.timeZone: Invalid value: "America/Los_Angeles": unknown time zone America/Los_Angeles

✅ 1

In general, cron takes the time zone setting of the machine where it's running. In the case of cronjob, that would be the kube-controller-manager's time zone: <https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/>

How can I set the timeZone????

Anyone??? The

kube-controller-manager

apparently is running on UTC and all the timezone names are showing as invalid value

I have tried to use the names starting with

Etc/*

as described in the url...

The CronJob "timecard-cron-job-local-localhost-prdt-ppd-loc" is invalid: spec.timeZone: Invalid value: "Etc/GMT+8": unknown time zone Etc/GMT+8

from the list https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

#rancher-desktop Join Slack