[helm] Should use jobs instead of pods in helm templates.

[Pangstar]

Helm Chart Version

0.64.388

What step the error happened?

None

Relevant information

Pods should not be directly referenced in helmcharts. Job wrapper should be applied to improve:

• Stability in case of NodeFailures: “The Job object will start a new Pod if the first Pod fails or is deleted (for example due to a node hardware failure or a node reboot).”
• Better retry mechanisms: You can specify exactly how many times a Pod is allowed to fail and restart.
• Multiple Successes: When you need a task to succeed X times total and then stop running.
• Parallelism: When multiple Pods can run at the same time

These are the locations of the pod definitions which should be updated to job.

https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/templates/minio.yaml#L106
https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte-bootloader/templates/pod.yaml#L3
https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/templates/tests/test-webapp.yaml#L3

ref: https://whyk8s.substack.com/p/why-use-jobs-and-not-bare-pods
ref: https://spacelift.io/blog/kubernetes-jobs
ref: https://kubernetes.io/docs/concepts/workloads/controllers/job/#bare-pods -> "we recommend that you use a Job rather than a bare Pod, even if your application requires only a single Pod. "

Relevant log output

No response