Fill gaps from assistant conversations: network volume datacenter scope - #841
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarify that network volumes are tied to a single datacenter and explain why Pod migration reports "no instances available" even when the same GPU type shows in the general deploy list.
Changes
storage/network-volumes.mdx: Add an upfront note that each volume lives in one datacenter and constrains any workload that attaches it, with a pointer to the migration section for multi-datacenter setups.pods/troubleshooting/pod-migration.mdx: Add a warning to the auto-migration option explaining that migration only searches the volume's datacenter, and describe the workaround.Context
Recurring assistant threads (network volume + Pod migration buckets) show users confused about why migration fails while matching GPUs appear elsewhere. The existing pages hinted at the constraint for Serverless multi-volume setups but never stated the single-datacenter lock upfront or tied it to the migration failure mode.