Jobs and Cronjobs lifecycle should be controlled by snoopy-operator

acmenezes commented 2 years ago

Currently the jobs are owned by snoopyJob CR and if a completed job is deleted by hand the controller restarts it. We need a solution to control the whole lifecycle of jobs avoiding those restarts and doing the proper cleanup.

[ ] One way to accomplish this is by using the status field to register all the Jobs and CronJobs that were completed.
[ ] With that the controller should always verify if the Job is registered in the status field as completed before initializing it.
[ ] Add a finalizer to the snoopyJob CR to make sure this routine is checked if the CR is deleted and also if someone tries to delete those Jobs by hand.

tokalevasant commented 2 years ago

Hi Alex, I would like to take this but would like to discuss exact requirements/process. Let's discuss this in our next meeting.

acmenezes commented 2 years ago

Sure @tokalevasant ! We can discuss in our meeting.

acmenezes commented 2 years ago

As per our triage meeting we agreed that a finalizer would the best way to accomplish this. The finalizer would be used by the reconciler for:

[ ] check the job status
[ ] if job completed it would delete the finalizer
[ ] update the CR status field with job completed

fennec-project / snoopy-operator

Jobs and Cronjobs lifecycle should be controlled by snoopy-operator #45