Coreweave migration deep dive
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill coreweave-migration-deep-diveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Migrate ML workloads from AWS/GCP/Azure to CoreWeave GPU cloud. Use when moving inference services from hyperscaler GPU instances, migrating training pipelines, or evaluating CoreWeave vs cloud GPU costs. Trigger with phrases like "migrate to coreweave", "coreweave migration", "move from aws to coreweave", "coreweave vs aws gpu".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, 440 tokens by cl100k_base, as published. Nobody here has run it
CoreWeave Migration Deep Dive
Cost Comparison
| Instance | AWS | CoreWeave | Savings |
|---|---|---|---|
| 1x A100 80GB | ~$3.60/hr (p4d) | ~$2.21/hr | ~39% |
| 8x A100 80GB | ~$32/hr (p4d.24xl) | ~$17.70/hr | ~45% |
| 1x H100 80GB | ~$6.50/hr (p5) | ~$4.76/hr | ~27% |
Migration Steps
Phase 1: Containerize
# If running on bare EC2/GCE, containerize first
docker build -t inference-server:v1 .
docker push ghcr.io/myorg/inference-server:v1
Phase 2: Adapt YAML for CoreWeave
Key changes from AWS EKS / GKE:
- Node affinity: Use
gpu.nvidia.com/classinstead ofnvidia.com/gpu.product - Storage: Use CoreWeave storage classes (
shared-ssd-ord1) - Networking: CoreWeave provides flat networking within VPC
Phase 3: Parallel Deploy
Run both old and new infrastructure simultaneously, gradually shift traffic.
Phase 4: Cut Over
Decommission old GPU instances after validation period.
Common Gotchas
| Issue | Solution |
|---|---|
| Different CUDA drivers | Match container CUDA to CoreWeave node drivers |
| Storage migration | Use rclone or rsync to move data to CoreWeave PVC |
| DNS changes | Update ingress/load balancer DNS |
| IAM differences | CoreWeave uses kubeconfig, not IAM roles |
Resources
Next Steps
This completes the CoreWeave skill pack. Start with coreweave-install-auth for new deployments.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.