[Bug]: migration job only runs if there is a change in values

[mikstew]

What happened?

We recently updated our helm chart version for the litellm proxy and saw that there was a job added to handle the database migration work. The job was successfully created and ran the first time, but didn't run on subsequent updates because the job already exists. Looking at the migrations-job.yaml template file I see that this checksum annotation exists: checksum/config: {{ toYaml .Values | sha256sum }}. The problem is that if nothing changes in the values.yaml file then that checksum doesn't change, so the job is not re-created. Is there a mechanism in place to ensure the migration job will run when required?

Relevant log output

No response

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

v1.55.10

Twitter / LinkedIn details

No response