Incorrect default for startingDeadlineSeconds

[bronger]

This is a...

• Feature Request
• Bug Report

Problem:

On https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/, it says “… and its startingDeadlineSeconds field is not set. The default for this field is 100 seconds.” I doubt the latter. It contradicts another expression above. Besides, this default is not mentioned in the API.

Proposed Solution:

Remove the sentence “The default for this field is 100 seconds.”

Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/

[tengqm]

Sad thing is .... the 100 seconds was hardcoded here: https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/cronjob/utils.go#L143

It is hand picked, and sounds like semantically equivalent to a default value.

Feel free to reopen.

[bronger]

No – the 100 is the number of failed restarts. This is hardcoded, but not the default of startingDeadlineSeconds which is nil as far as I can see.

[tengqm]

Alright. Reopening.

[rajeshdeshpande02]

@bronger @tengqm I will pick this for fixing in the documentation.

[anbugit004]

Is anyone have a look and let me know if you have any idea on the below things:

How many pods can be run in kubernetes master nodes in HA Cluster

For example there is 10 node cluster ( 3 master + 7 worker nodes are available)

Can you please tell us the maximum number of pods can assign it to each master nodes

[daminisatya]

/close

[k8s-ci-robot]

@daminisatya: Closing this issue.

In response to this:

/close

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.