Schema changes of content model changes lost after pod restart

We have deployed strapi on Kubernetes, when we make schema changes somehow pod gets retarted with exit code 0 and we lose our data. We have attached PVC for /public/uploads but content model changes gets stored on pod filesystem on different path so I want to know how can we avoid this?
We generally create new docker image once schema changes are done but before that if pod gets restarted we lose our all data and we need to do all the rework. Please let us know the permanent solution for this

This topic has been created from a Discord post (1268573117115273319) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord