-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
When using jenkins kubernetes-plugin each jenkins job in my cluster takes an additional 2 minutes to start. This is due to the job kicking-off a new pod and awaiting the pod to start all containers and register itself with the master.
Is there a way to have a pod created and available for the next job? Each of our pipelines is constructed from a slightly different podTemplate() so I understand I would need to have an idle pod for each podTemplate().
Any updates on this? Or any workarounds you could share?