From ff618193a929ae42380726e6ef83309f21c8ca7b Mon Sep 17 00:00:00 2001 From: Maciej Szulik Date: Wed, 2 Feb 2022 18:11:25 +0100 Subject: [PATCH] Add more clarification about tzdata --- .../3140-TimeZone-support-in-CronJob/README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md b/keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md index a779c163303..bd1713b1686 100644 --- a/keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md +++ b/keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md @@ -126,9 +126,10 @@ CronJobs can be created per user. ### CronJob API The `.spec` for a CronJob is expanded with a new `timeZone` field which allows -specifying the name of the time zone to be used. Missing or empty value of the -field indicates the current behavior, which relies on the time zone of the -kube-controller-manager process. +specifying the name of the time zone to be used, the list of valid time zones +can be found [in tz database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +Missing or empty value of the field indicates the current behavior, which relies +on the time zone of the kube-controller-manager process. In the API code, that looks like: @@ -145,8 +146,9 @@ type CronJobSpec struct { } ``` -The value provided in `TimeZone` field will be validated against the embedded -golang timezone database. +The value provided in `TimeZone` field will be validated against the embedded golang +timezone database, which will result in the `kube-apiserver` and `kube-controller-manager` +binaries growing by roughly extra 500kB. ### CronJob controller