coreweave-multi-env-setup

# CoreWeave Multi-Environment Setup ## 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.CW_TOKEN_PROD!, gpuType: "A100_PCIE_80GB", scaleToZero: false, replicas: [2, 10], }, }[env]); ``` ## Environment Files ```bash # Per-env files: .env.development, .env.staging, .env.production CW_API_ENDPOINT_{DEV|STG|PROD}=https://k8s.{ord1|ord1|las1}.coreweave.com CW_TOKEN_{DEV|STG|PROD}=<service-account-token> CW_NAMESPACE={app-dev|app-staging|app-prod} CW_GPU_TYPE={L40|A100_PCIE_40GB|A100_PCIE_80GB} `...