rescheduleCriticalSeconds limited to max 98 seconds

[martin2176]

scheduleStrategy: type: Adaptive adaptive: rescheduleCriticalSeconds: 180

Invalid value: 180: rescheduleCriticalSeconds < 0 or rescheduleCriticalSeconds > 98 is not permitted I have 4 subsets . Adding each subset lower the allowed value of reschedulecriticalseconds.

Can we allow user to specify a reasonable time such as 5 minutes.? Cloud Kubernetes deployments take atleast 2 minutes to spin up a node in response to an autoscaler event

[veophi]

sounds good

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[martin2176]

Will someone triage this and approve/reject ?

[zmberg]

/reopen

[kruise-bot]

@zmberg: Reopened this issue.

In response to this:

/reopen

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.

[zmberg]

@caniszczyk I thinks it's good. Can you submit a pr for this?

[zmberg]

#823

[martin2176]

great and thank you.( I have not tested it)

[martin2176]

what is the max value that is now allowed for rescheduleCriticalSeconds? Would the documentation be eventually updated to reflect this