| Hello, not having a timeout parameter on the jnlp agent connection to master might be causing further issues when (on kubernetes) the jenkins-master container is moved, inducing a 2-3 minutes downtime of master while the jenkins-master pod boots on a different kubernetes node during resource scaling and pod orchestration. This appears to result in job pods (live agents/slaves) failing due to no connection to master. In kubernetes this results in a job failure, rather than a job being paused and waiting for the master to become available again. This in turn results in job pods not being cleaned up due to the pods being left in `Error` state. JENKINS-54540 Hoping to bridge the gap if there is one, this is probably affecting everybody that runs on kubernetes/gke/aks/azurek8s. |
