Cloudbees Jobs are getting struck after kubernetes Pod gets restarted

5/7/2021

We have cloudbees hosted on a Kubernetes environment and each application has it's own cloudbees controller(Master). When the pod on which master is running gets restarted , (Whatever maybe the reason of restart). The Jobs that were running at the time of pod restart are getting struck. They can't be aborted and they won't even progress. We found one way , that is restarting the master again would help us abort the Jobs. Can anyone help me in this?

-- Maheedhar Talluri
cloudbees
kubernetes

0 Answers