coreweave-multi-env-setup
Configure CoreWeave across development, staging, and production environments. Use when setting up multi-environment GPU infrastructure, separating namespaces, or managing per-environment GPU quotas. Trigger with phrases like "coreweave environments", "coreweave staging", "coreweave multi-env", "coreweave namespace setup". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coreweave-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CoreWeave Multi-Environment Setup > **Community-contributed.** Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. ## Overview CoreWeave GPU cloud requires strict environment separation to control infrastructure costs and prevent resource contention. Each environment maps to an isolated Kubernetes namespace with its own GPU quota, scaling policy, and access controls. Development uses cheaper GPU tiers for iteration speed, staging mirrors production GPU types for accurate benchmarking, and production runs full-scale with no scale-to-zero to guarantee inference latency SLAs. ## Environment Configuration ```typescript const coreweaveConfig = (env: string) => ({ development: { namespace: "app-dev", apiEndpoint: process.env.CW_API_ENDPOINT_DEV!, token: process.env.CW_TOKEN_DEV!, gpuType: "L40", scaleToZero: true, replicas: [0, 1], }, staging: { namespace: "app-staging", apiEndpoint: process.env.CW_API_ENDPOINT_STG!, token: process.env.CW_TOKEN_STG!, gpuType: "A100_PCIE_40GB", scaleToZero: true, replicas: [0, 2], }, production: { namespace: "app-prod", apiEndpoint: process.env.CW_API_ENDPOINT_PROD!, token: process.env
- Overview
- Environment Configuration
- Environment Files
- Environment Validation
- Promotion Workflow
- Environment Matrix
- Error Handling
- Resources
- Next Steps
kubectl -n app-dev get inferenceservice my-model -o jsonpath='{.status.conditions}'
kustomize build k8s/overlays/staging | kubectl apply -f -
curl -X POST https://staging.myapp.coreweave.cloud/v1/predict -d @test-payload.json
kustomize build k8s/overlays/prod | kubectl apply -f -
kubectl -n app-prod rollout status deployment/my-modelWhat does the coreweave-multi-env-setup skill do?
Configure CoreWeave across development, staging, and production environments. Use when setting up multi-environment GPU infrastructure, separating namespaces, or managing per-environment GPU quotas. Trigger with phrases like "coreweave environments", "coreweave staging", "coreweave multi-env", "coreweave namespace setup". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coreweave-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.