You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To generate CronJob schedule expressions, you can also use web tools like [crontab.guru](https://crontab.guru/).
@@ -318,74 +317,76 @@ For another way to clean up jobs automatically, see [Clean up finished jobs auto
318
317
319
318
<!--
320
319
### Time zones
321
-
322
-
For CronJobs with no time zone specified, the {{< glossary_tooltip term_id="kube-controller-manager" text="kube-controller-manager" >}} interprets schedules relative to its local time zone.
A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.
346
+
-->
347
+
Go 标准库中的时区数据库包含在二进制文件中,并用作备用数据库,以防系统上没有可用的外部数据库。
331
348
332
349
<!--
333
-
If you enable the `CronJobTimeZone` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
334
-
you can specify a time zone for a CronJob (if you don't enable that feature gate, or if you are using a version of
335
-
Kubernetes that does not have experimental time zone support, all CronJobs in your cluster have an unspecified
336
-
timezone).
350
+
## CronJob limitations {#cron-job-limitations}
337
351
338
-
When you have the feature enabled, you can set `.spec.timeZone` to the name of a valid [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). For example, setting
339
-
`.spec.timeZone: "Etc/UTC"` instructs Kubernetes to interpret the schedule relative to Coordinated Universal Time.
A time zone database from the Go standard library is included in the binaries and used as a fallback in case an external database is not available on the system.
373
-
-->
374
-
Go 标准库中的时区数据库包含在二进制文件中,并用作备用数据库,以防系统上没有可用的外部数据库。
375
-
376
-
<!--
377
-
## CronJob limitations {#cron-job-limitations}
378
-
379
381
### Modifying a CronJob
382
+
380
383
By design, a CronJob contains a template for _new_ Jobs.
381
384
If you modify an existing CronJob, the changes you make will apply to new Jobs that
382
385
start to run after your modification is complete. Jobs (and their Pods) that have already
383
386
started continue to run without changes.
384
387
That is, the CronJob does _not_ update existing Jobs, even if those remain running.
0 commit comments