Repository navigation
docs: add guides for migrating to Runpod from 14 other platforms - #968
Open
lukepiette wants to merge 3 commits into
Open
lukepiette wants to merge 3 commits into
lukepiette wants to merge 3 commits into
Conversation
Add a "Migrate to Runpod" section: an overview page and a guide each for Vast.ai, Lambda, CoreWeave, Paperspace and DigitalOcean, Modal, Replicate, Baseten, fal, Together AI, Fireworks AI, Hugging Face, AWS, Google Cloud and Azure. The existing Cog and OpenAI migration pages move into the new nav group, and the agent skills page lists the runpod-cloud-migrate skill. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
A mechanical pass validated every runpodctl invocation, REST v2 body, SDK symbol and Terraform block against the command surface, the OpenAPI spec, the runpod package source and the provider schemas. Four adversarial passes re-checked the other platforms' facts against their live docs and walked each migration end to end. Data-loss and billing fixes: - CoreWeave: shutdown no longer deletes the PVC with the Deployment - Lambda: copy root-volume data before terminating instances - Google Cloud: warn that terraform import can force Pod replacement - Vast.ai: shutdown now deletes Deployments; rsync step needs a key the Pod accepts - Baseten: orchestrator polls a long job instead of resubmitting it Runpod-side corrections: - vLLM worker settings the current worker ignores (structured output, speculative decoding), and routes it does serve (Responses, Messages) - Remove Public Endpoints that are not in the live catalog - Custom handlers point at the cached-model path so weights are not downloaded on each cold start - Load-balancing endpoints: set ports, and a timeout within the request limit - serverless update scaling flags, zero-balance behavior, global networking scope Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
runpodctl v3.1.1 lists config as deprecated. Checked all 804 runpodctl invocations in the guides and playbooks against a v3.1.1 build: these two rows were the only ones using a deprecated command. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
lukepiette
marked this pull request as ready for review
November 14, 2026 20:41
lavanya-gunreddi
approved these changes
Nov 15, 2026
nick4fake
reviewed
Nov 16, 2026
nick4fake
left a comment
Contributor
There was a problem hiding this comment.
I think this should go to KB, not docs. If it stays here:
- hold the merge until runpod-plugins-official#127 is merged and released, all pages point to
runpod-cloud-migrate//runpod:migrate-cloud codexisn't a valid--clientfornpx @runpod/mcp-server add(overview, vast-ai and aws tabs), Codex gets MCP from the plugin. Maybe move this block to a snippet- aws, SageMaker on LB endpoint:
serve.pykeeps the model and input on CPU, needsmap_location="cuda"and the tensor on cuda likeinference.py - aws step 5: A4000 just to run
aws s3 sync, a CPU pod is enough (--compute-type cpu) - ECR on serverless: I wouldn't publish "test first", let's check which source is right and fix it
- lots of numbers copied from other pages (spend limit, LB limits, payload sizes etc), better to link them
I only read overview, vast-ai, modal and aws.
| npx @runpod/mcp-server@latest add --client CLIENT_ID | ||
| ``` | ||
|
|
||
| Replace `AGENT_ID` and `CLIENT_ID` with your agent's ID, for example `cursor` or `codex`. |
Contributor
There was a problem hiding this comment.
codex isn't a --client id, cursor or opencode instead
This branch was successfully deployed
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.
What
Adds a "Migrate to Runpod" section to the docs: an overview page and one end-to-end guide per platform.
Every guide has the same shape: a concept map, what works differently and what has no direct equivalent (in both directions), eight steps from inventory to shutdown with before and after code, reference maps (CLI, API, config fields, env vars, statuses), a prompt for coding agents, and troubleshooting.
Other changes:
docs.json: new "Migrate to Runpod" nav group above Reference. The existing Cog and OpenAI migration pages move into it (URLs unchanged, so no redirects).get-started/agent-skills.mdx: lists therunpod-cloud-migrateskill and the/runpod:migrate-cloudcommand.Covers DR-1650 (Vast.ai guide).
How it was checked
mint broken-linkspasses.runpodctlcommands that are in the CLI reference here.Not done, and worth a reviewer's attention
terraform applywas created, and no before/after program was executed. A live pass on the Runpod half of a few guides (Vast.ai, Modal, AWS, one vLLM base URL swap) is the highest-value check before publishing.tutorials/pods/use-private-ecr-images.mdxsays Serverless uses a different mechanism. The AWS guide tells readers to test first.Depends on
runpod/runpod-plugins-official#127 adds the
runpod-cloud-migrateskill and/runpod:migrate-cloudcommand that every guide's "Migrate with a coding agent" section points to. That should merge and release before this publishes.🤖 Generated with Claude Code