Update information about CronJob's unsupported time zone field #49327
Conversation
k8s-ci-robot
added
do-not-merge/hold
k8s-ci-robot
added
the
size/XS
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Maciej Szulik <[email protected]>
soltysh
force-pushed
the
tz_validation
branch
from
2294aa3 to
5f6ae8e
Compare
k8s-ci-robot
added
size/S
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
We've decided not to land kubernetes/kubernetes#129510 at all, but we want to change the docs, entirely removing the wording about what is allowed with regards to |
|
/hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
|
/assign @sftim |
| [warning](/blog/2020/09/03/warnings/) to the client. | ||
| is **not officially supported** (and never has been). If you try to set a schedule | ||
| that includes `TZ` or `CRON_TZ` timezone specification, Kubernetes will fail to | ||
| create or update the resource with a validation error. Users are encouraged to use |
There was a problem hiding this comment.
Style nit:
| create or update the resource with a validation error. Users are encouraged to use | |
| create or update the resource with a validation error. You should specify time zones using the |
There was a problem hiding this comment.
Maybe we should mention that the early beta CronJob API didn't include that enforcement, so that people can understand how come they have TZ set in their CronJob.
Description
This is accompanying the change from kubernetes/kubernetes#129510 which entirely forbids
CRON_TZandTZvariables in.spec.scheduleof a cronjob./hold
for the k8s PR to merge first