Wrong timezone?

[digitalocean]

Wrong timezone?

[timoreimann]

Does that mean, that in order to run 12:00 in my Berlin time i need to specify 10:00 in my cronjob?

That's correct: as the clusters run on UTC, you will need to subtract 2 hours from your local Berlin / CEST time when considering what time you need to pass to kubectl.

Or is it just kubectl displaying wrong time calculation and the job was actually executed as scheduled?

I couldn't spot a wrongly displayed calculation by kubectl. As long as you keep thinking in UTC, things should be correct.

[mishushakov]

So, here my cronjob triggered 2 hrs later:

The time is UTC, right?

[timoreimann]

Yes, the time is UTC.

It looks correct to me: this is what I get when I kubectl get your dialogflow-gateway-reporter cronjob right now:

NAME                          SCHEDULE     SUSPEND   ACTIVE   LAST SCHEDULE   AGE
dialogflow-gateway-reporter   0 12 1 * *   False     0        7h36m           9h

And this is the time I end up with if I subtract those 7h36m from now:

$ date -u -d "- 7 hours - 36 mins"
Thu Aug  1 12:00:42 UTC 2019

I'm guessing your local machine isn't configured to UTC but CET?

[mishushakov]

Hey @timoreimann ✌️
I feel completely stupid now...

So, this is the time setting on my computer:

This is the output of date and date -u command on my local machine and alpine pod:

the time on my wrist is 18:xx

Does that mean, that in order to run 12:00 in my Berlin time i need to specify 10:00 in my cronjob?
Or is it just kubectl displaying wrong time calculation and the job was actually executed as scheduled?

Thanks.

[mishushakov]

👍