Repository navigation
Add documentation for external volumes feature - #963
lavanya-gunreddi wants to merge 5 commits into
Conversation
Document the process and requirements for using external volumes with S3-compatible buckets on Runpod.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
coreykasten
left a comment
There was a problem hiding this comment.
A few accuracy fixes. Several statements are out of date after recent API and host changes (attaching and detaching volumes on existing Pods, credential updates reaching running mounts), and a couple of terms suggest implementation details we haven't documented publicly.
|
Thanks @coreykasten! Addressed all 12 comments in af17142. Ready for another look. |
|
|
||
| </Note> | ||
|
|
||
| An external volume lets you mount an S3-compatible bucket you already own on Pods and Serverless workers, in any data center. Your data stays in your bucket. Runpod doesn't copy, move, or delete it, and doesn't charge a storage fee. You pay your storage provider directly. |
There was a problem hiding this comment.
Non-blocking: "in any data center" here and on line 20 reads a little broader than "GPU and CPU Pods in Secure Cloud" further down. Maybe "in any Secure Cloud data center". Fine to leave as is, since the Pods section states the limit.
Document the process and requirements for using external volumes with S3-compatible buckets on Runpod.