Hello
I am running into a confusing issue where persistent volume data in my Okteto dev environment seems to vanish after re-deploying the stack / restarting the environment. I was under the impression that data stored in
/data
(or similar bound volumes) would survive across restarts unless explicitly deleted, but in my case; it resets unexpectedly.
I have checked my okteto.yaml
and docker-compose.yml
files to ensure I am mounting a named volume; not a temporary one. Still, whenever I redeploy with okteto up
, the volume seems to reset—leading to data loss in development; like missing files / empty databases.
Is there a setting I’m overlooking in Okteto that ensures persistence across lifecycle events? Checked Volume Snapshots | Okteto Documentation) guide related to this and found it quite informative.
Is this an expected behavior tied to how Okteto handles ephemeral dev environments / is there a recommended way to define truly persistent volumes for local / cloud-based dev flows?
Any help clarifying this behavior or pointing to a best practice would be greatly appreciated!
Thank you !!