Skip to content

Commit ff61819

Browse files
committed
Add more clarification about tzdata
1 parent 09a41a1 commit ff61819

File tree

1 file changed

+7
-5
lines changed
  • keps/sig-apps/3140-TimeZone-support-in-CronJob

1 file changed

+7
-5
lines changed

keps/sig-apps/3140-TimeZone-support-in-CronJob/README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -126,9 +126,10 @@ CronJobs can be created per user.
126126
### CronJob API
127127

128128
The `.spec` for a CronJob is expanded with a new `timeZone` field which allows
129-
specifying the name of the time zone to be used. Missing or empty value of the
130-
field indicates the current behavior, which relies on the time zone of the
131-
kube-controller-manager process.
129+
specifying the name of the time zone to be used, the list of valid time zones
130+
can be found [in tz database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
131+
Missing or empty value of the field indicates the current behavior, which relies
132+
on the time zone of the kube-controller-manager process.
132133

133134
In the API code, that looks like:
134135

@@ -145,8 +146,9 @@ type CronJobSpec struct {
145146
}
146147
```
147148

148-
The value provided in `TimeZone` field will be validated against the embedded
149-
golang timezone database.
149+
The value provided in `TimeZone` field will be validated against the embedded golang
150+
timezone database, which will result in the `kube-apiserver` and `kube-controller-manager`
151+
binaries growing by roughly extra 500kB.
150152

151153
### CronJob controller
152154

0 commit comments

Comments
 (0)