Closed Jari608 closed 1 year ago
The airbyte-bootloader is supposed to exit after setting things up. Can you confirm that it isn't configured to restart after a successful exit?
The airbyte-bootloader is not configured to restart after a successful exit. The manifest of the airbyte-bootloader pod (shortly visible in Argo CD before the pod restarts again) contains the following setting:
restartPolicy: Never
Is there any solution yet? I have the same issue. It is working for me now because I have set the airbyte-bootloader job to skip in argocd after the first deployment but this should not be a permanent solution.
I figured out why the job restarts indefintley.
The Job is configured with ttlSecondsAfterFinished which is documented here. This causes the Job itself to be removed 5 seconds after the job is finished.
Due to the ttlSecondsAfterFinished setting ArgoCD will re-create it when it is deleted.
Possible solution is it to setup a PostSync hook with a hook-delete-policy.
See also https://serverfault.com/questions/1111989/why-does-argocd-keep-re-syncing-my-job
Hi @tim-werner
We don't support kustomize anymore, but this is probably still relevant in helm charts. Is this still an issue that you are facing?
Hi @cpdeethree,
I have tried out the helm charts and the issue is not present anymore. You can close the issue. Thx.
Great, thank you!