Does fargate charge for complete jobs scheduled by cronjob after associated pod is terminated?

Question

I deployed a cronjob in fargate eks cluster. The cronjob keeps 10 successful jobs and 2 failed jobs. Any pod created from a scheduled job is immediately terminated after the job completes.
Unlike my expectation, I was told I'll be still charged for the job until all resources for the job is cleaned up because Fargate keeps a spot instance to a job even though it completed. So, I have to set ttlSecondsAfterFinished to get all resource are cleaned up. Problem I have is due to short ttl, I can't tell whether my previous job succeeded or failed after set ttl time. 
Is this true?

Answer

Hello,

With Kubernetes Jobs, when a Job completes, no more Pods are created, but the Pods are usually not deleted either. Keeping them around allows you to still view the logs of completed pods to check for errors, warnings, or other diagnostic output.

In EKS/Fargate the lifecyle of the Fargate node and costs are tied to the pod. As long as the pod is not removed the fargate node supporting it will be there. Given the pod is not deleted you are charged for it.

There are some tools in the Kubernetes ecosystem that can help with job cleanup. Some examples are below.

https://github.com/lwolf/kube-cleanup-operator

https://github.com/aramse/k8s-job-reaper

A fargate logging configuration should be leveraged to send the logs to a centralized location like Cloudwatch or OpenSearch before the pod is removed.

Hope that helps.

Answer

Kubectl get pods will show the pods associated with the job. Here's an example

```
kubectl get pods --selector=batch.kubernetes.io/job-name=examplejob
```

The documentation below outlines this.

https://kubernetes.io/docs/concepts/workloads/controllers/job/#running-an-example-job

Does fargate charge for complete jobs scheduled by cronjob after associated pod is terminated?

Relevant content