Job termination required due to Runner State change (K8s Autoscaler)
Jiwon Jeon
Contributor
After a certain period of time, when Runner Job's status goes from ONLINE to inactive, the API request returns 400 codes, and the logs that fail have been identified. After that, the pod will continue to be a zombie state that does not actually execute the pipeline, so I would like to add the task of cleaning up the pod in this state.