This is a Bug Report
Problem: startingDeadlineSeconds can be set to any value, but the CronJob Controller checks things every 10s. If it's set to any value less than 10s the CronJob will be never scheduled.
Proposed Solution: Force the value to be always greater than 10, or warn people there are non-working values
Page to Update:
https://kubernetes.io/es/docs/concepts/workloads/controllers/cron-jobs/
Kubernetes Version: 1.15.12
/kind cleanup
/language en
/triage accepted
Thanks @juan-vg
I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may _eventually_ honor any setting for startingDeadlineSettings; however, we want to document the shortcoming right now.
Specifically I would add a caution callout, with text similar to:
if
startingDeadlineSecondsis set to a value less than 10 seconds then the CronJob may not be scheduled.
/good-first-issue
/sig apps
@sftim:
This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
I recommend adding a warning. There is a v2 controller for CronJob arriving in Kubernetes v1.20 that may _eventually_ honor any setting for
startingDeadlineSettings; however, we want to document the shortcoming right now.Specifically I would add a caution callout, with text similar to:
if
startingDeadlineSecondsis set to a value less than 10 seconds then the CronJob may not be scheduled./good-first-issue
/sig apps
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/assign