> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/pods-running-jobs-or-scripts-remain-after-completed-state.md).

# Pods Running Jobs or Scripts Remain After Completed State

### Issue <a href="#issue" id="issue"></a>

Pods launched and completed for running jobs or scripts remain even after completion state. They do not automatically clean themselves after completion

### Cause <a href="#cause" id="cause"></a>

Kubernetes doesn't have an automated way to clean up jobs without enabling a feature flag on the master (which isn't possible on *most* managed Kubernetes services). Spinnaker project also opted to *not* clean up jobs on completion because we found that our primary users didn't have any logging infrastructure in place to view logs after the fact which means that debugging jobs would be impossible for some users.