A one-off database migration Job failed and must be run again. What is the appropriate application approach?

Jobs are completion-oriented records of finite runs. After failure, application practice is to launch another Job execution—often by creating a new Job object or recreating the prior one—rather than converting the work into a long-running Deployment or DaemonSet. Service traffic policy is unrelated to Job reruns.