Agent skill · software engineering · jeremylongshore
coreweave-upgrade-migration
Upgrade CoreWeave deployments and migrate between GPU types.
Why this skill is useful
Provides specific migration scripts and procedures for upgrading CoreWeave deployments that the AI wouldn't reliably generate on its own.
What it needs
Requires kubectl installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CoreWeave Upgrade & Migration Community-contributed. Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. Overview CoreWeave is a GPU-specialized cloud provider running Kubernetes-native infrastructure. Migrations involve upgrading between GPU instance types (A100 to H100), updating CUDA driver versions, and handling Kubernetes API version changes across namespaces. Tracking API versions is critical because CoreWeave's instance type labels and resource quotas change between platform releases, and deploying to a deprecated instance class will cause scheduling failures. Version Detection Migration Checklist [ ] Review CoreWeave release notes for deprecated instance types [ ] Audit all deployments for gpu.nvidia.com/class node selectors [ ] Verify CUDA version compatibility with target GPU (see matrix below) [ ] Update container base images to match new CUDA/cuDNN requirements [ ] Test inference latency on new GPU type in staging namespace [ ] Update resource requests (nvidia.com/gpu) for new instance memory [ ] Migrate persistent volumes if switching regions or availability zones [ ] Update Kubernetes API version in manifests (e.g., apps/v1 changes) [ ] Validate HPA scaling behavior on new instance type throughput [ ] Run canary deployment with traffic split before full cutover Schema Migration Rollback Strategy Prerequisites A versioned manifest, compatible CUDA/image matrix, and capacity confirmation for the target GPU or cluster change. Staging evaluation evidence, named migration owner, and a verified previous deployment revision. Backup/retention approval for any PVC, checkpoint, or model-artifact move. Instructions 1. Inventory current selectors, images, API versions, volumes, quotas, and service SLOs. 2. Update the manifest in staging, validate server-side, and run compatibility and performance checks. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coreweave-upgrade-migration