-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Kubernetes plugin 1.30.1
Jenkins 2.263.4 LTS
When Jenkins is launching a new slave/agent pod, it never times out and keep trying to launch a new pod when the current is failing.
For example, we had an issue of miss configuration made the agent pod to be created in a namespaces where there're no pull credentials. In this case we had a cron job which got stuck and kept trying to created a pod for 2 days (until manually aborted), although the issue has been already resolved. It didn't get the code update since the job has to be stopped and rebuilt.
I went through the whole relevant documentation to find proper timeout setting, but nothing worked. I thought slaveConnectTimeout should do the job, but it didn't help, as well as setting org.csanchez.jenkins.plugins.kubernetes.PodTemplate.connectionTimeout system property.
What I'm looking for is an option to set a timeout that kills the jobs if it can't launch an agent pod after x seconds.
- is related to
-
JENKINS-68409 kubernetes plugin can create a new pod every 10s when something wrong
-
- Reopened
-
Have you considered trying the timeout option for the whole pipeline?
https://www.jenkins.io/doc/book/pipeline/syntax/#options