File tree Expand file tree Collapse file tree 1 file changed +7
-5
lines changed
keps/sig-apps/3140-TimeZone-support-in-CronJob Expand file tree Collapse file tree 1 file changed +7
-5
lines changed Original file line number Diff line number Diff line change @@ -126,9 +126,10 @@ CronJobs can be created per user.
126
126
### CronJob API
127
127
128
128
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.
132
133
133
134
In the API code, that looks like:
134
135
@@ -145,8 +146,9 @@ type CronJobSpec struct {
145
146
}
146
147
```
147
148
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.
150
152
151
153
### CronJob controller
152
154
You can’t perform that action at this time.
0 commit comments