### Steps to reproduce

_Please write down the steps to reproduce. Try to write down all necessary preconditions (what permissions do you have, are other users involved?). Example:_

1. Deploy OpenProject via helm

2. Wait for an update of the OpenProject slim container

3. Take down the Kubernetes cluster node that runs OpenProject

4. Wait for another node to take over and pull the newer slim image


### What is the buggy behavior?

_Please describe the bug in as much detail as possible. Example:_

* The web workers stop working because of pending migrations

* The seeder is not run automatically 


### What is the expected behavior?

_Describe how the application should behave like. Example:_

1. The Begin of the insertionhelm chart is tiedEnd of the insertion Begin of the deletion seeder runs automatically so that you not needEnd of the deletion to Begin of the insertiona specific version

2. We provide new helm chart versions when OpenProject version is bumped


End of the insertion Begin of the deletion trigger the seeder manually if the slim container has been upgraded




End of the deletion ###

**OpenProject installation type**

* Begin of the deletion [ ]End of the deletion Hosted cloud edition Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Begin of the deletion [ ]End of the deletion Packaged installation Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * What distribution?

* Begin of the deletion [ ]End of the deletion Docker All-in-one container Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Begin of the deletion [ ]End of the deletion Docker-compose installation Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Begin of the deletion [x]End of the deletion Other helm deployment