Issue with Autoscaled Runners on Kubernetes – Online/Offline Status and Resource Cleanup

[POLU ANIL KUMAR REDDY]

Hi Team,

We are currently running our runners on Kubernetes using the Autoscaler, with deployments under different names across separate clusters.

Although both runners consistently show as “Online,” we’ve encountered an issue when triggering multiple pipelines with specific labels. In these instances, one runner remains online while the other switches to offline status.

Additionally, we’ve noticed that multiple jobs and pods are continuously running, but they are not being deleted automatically as expected. As a result, we are manually deleting these jobs and pods each time and reapplying the values.

Could you please assist us in resolving these issues?

Thank you for your support.

Best regards,
Anil Reddy

[Theodora Boudale · Accepted solution]

Hi Anil,

I replied to the other post you created here:

• https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-Kubernetes-runners/qaq-p/2780347

Please check my reply to this other post and let me know if you have any questions.

Kind regards,
Theodora