Scenario(s) that I've personally experienced in GoCD:
1. *Job is actually hung or it doesn't write anything to stdout / stderr
for a long time, which is the definition of job hung in GoCD* -- GoCD
still doesn't kill the job or reschedule it. If you've configured job hung
timeout then
Hello -- Curious to know if anyone has seen this behavior before -
GoCD version v20.2.0
Kubernetes Elastic Agent Plugin v3.2.0-187
We noticed in the console.log file for an actively running job, midway
through running there is a request to create a new pod for the job and the
job starts
