Skip to content

Commit 2c5cb62

Browse files
authored
Merge pull request #49327 from soltysh/tz_validation
Update information about CronJob's unsupported time zone field
2 parents 3b63b36 + d0fa9da commit 2c5cb62

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

content/en/docs/concepts/workloads/controllers/cron-jobs.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ The `.spec.schedule` field is required. The value of that field follows the [Cro
6060
# │ │ │ ┌───────────── month (1 - 12)
6161
# │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday)
6262
# │ │ │ │ │ OR sun, mon, tue, wed, thu, fri, sat
63-
# │ │ │ │ │
63+
# │ │ │ │ │
6464
# │ │ │ │ │
6565
# * * * * *
6666
```
@@ -192,13 +192,10 @@ A time zone database from the Go standard library is included in the binaries an
192192
### Unsupported TimeZone specification
193193

194194
Specifying a timezone using `CRON_TZ` or `TZ` variables inside `.spec.schedule`
195-
is **not officially supported** (and never has been).
196-
197-
Starting with Kubernetes 1.29 if you try to set a schedule that includes `TZ` or `CRON_TZ`
198-
timezone specification, Kubernetes will fail to create the resource with a validation
199-
error.
200-
Updates to CronJobs already using `TZ` or `CRON_TZ` will continue to report a
201-
[warning](/blog/2020/09/03/warnings/) to the client.
195+
is **not officially supported** (and never has been). If you try to set a schedule
196+
that includes `TZ` or `CRON_TZ` timezone specification, Kubernetes will fail to
197+
create or update the resource with a validation error. You should specify time zones
198+
using the [time zone field](#time-zones), instead.
202199

203200
### Modifying a CronJob
204201

0 commit comments

Comments
 (0)