Ran into this when trying to use persistent disks as a backend for Rails' ActiveStorage. Usually you have a background worker in that setup that takes care of creating thumbnails or purging files once the db object has been stroyed. That obviously doesn't work if the background worker and web process don't have access to the same Disk. Feels like Disks would have to be a top-level service like Postgres that can be linked to web services / background workers.

Anurag Goel What does "planned" mean exactly? Considering this has been planned since 2020, should we consider this as "never going to happen"?

I think context that needs to be captured is connecting the same persistent disk to an app and a cron job. For example- I'm creating a message in https://getstream.io/ and the message has an image. This image is stored in a persistent disk in render. When I try to access this file from the cron job, it doesn't work because its not connected to the same volume.

This is essential for some of the services I need to create, look forward to it 👍