Select the data center region, hardware, and firmware for a Virtual Server
Region
Virtual Servers may be deployed across any of data center regions. CoreWeave's data center regions are broken up into three geographical buckets - US East, Central and West. Each provides redundant 200Gbps+ public Internet connectivity from Tier 1 global carriers, and are connected to each other using 400Gbps+ of dark fiber transport to allow for easy, free transfers of data within CoreWeave Cloud.
Note
It is generally advised to select the data center region closest to your location.
Deployment method:CoreWeave Cloud UI
From the CoreWeave Cloud UI Virtual Server deployment menu, click the Region expandable, then select the region in which to host the Virtual Server by clicking on it.
Deployment method:Kubernetes CLI
Selecting a region for your Virtual Server is simple using the Kubernetes manifest file.
The data center region you'd like to use is configured by setting its label under the region selector in the spec section of the manifest.
Data center region configuration options
Variable name
Variable type
Description
Default value
region
String
The label of the data center in which you'd like to deploy the Virtual Server.
3
In the example below, the Chicago (ORD1) data center is chosen under spec.region.
From the CoreWeave Cloud UI Virtual Server deployment menu, click the Hardware expandable, then select the hardware kind (GPU or CPU) and the hardware itself. Clicking the GPU tab will display all available GPU options, and clicking the CPU tab will do the same for CPU types.
The GPU Count, Core Count, and Memory amount (in Gi) are chosen using the sliders at the bottom of the section.
Each hardware selector also displays a meter registering the availability of that hardware type per region.
Resource definition (YAML only)
In the CRD's YAML manifest, the .spec.resources.definition field is used as a way to describe the chosen resources. The default value of this field is a - this is just a placeholder, which can be changed to any string.
Using the Kubernetes CLI deployment method, hardware options are configured under the resources block in the Virtual Server manifest (e.g., virtual-server.yaml).
In this method, hardware designations are defined as a kind of resource, just like CPU type, CPU core count, GPU count, and memory.
Hardware and resource configuration options
Each of the following fields will be configured underneath the resources block in the YAML manifest.
Field name
Type
Description
resources
Array
The top-level field.
Defines the resources and devices allocated to the Virtual Server.
The Virtual Server's hardware and resource options are configured as variables passed into the Virtual Server Terraform module.
Hardware and resource configuration options
The following table describes the variables usable for Virtual Server configuration, as well as whether or not the module defines any default values for them.
Variable name
Variable type
Description
Default value
vs_cpu_count
Integer
Number of CPUs requested.
3
vs_gpu_enable
Boolean
Enable GPU (or not) for this Virtual Server.
true
vs_gpu
String
Quadro_RTX_4000
vs_gpu_count
Integer
1
vs_memory
String
Memory specified for the Virtual Server, in Gi (eg. 16Gi).
Firmware identification information for Virtual Servers is set by the Virtual Machine Instance (VMI). The firmware's UUID (MAC address) is set by the BIOS, and its system-serial number is set by the VMI's SMBIOS.
The firmware's UUID defaults a randomly-generated alphanumeric string. Both numbers are static across Virtual Server restarts.
It is optional to set these; if not set, they will have randomly-generated defaults.
Note
You can read more about virtual hardware firmware configuration in the Kubevirt documentation, or see how its exposure is implemented in CoreWeave by viewing our API reference.
Deployment method:CoreWeave Cloud UI
In the Cloud UI, firmware options must be set using the YAML editor. Firmware options are not currently exposed through the YAML manifest by default, so they must be added to the key-value map in the manifest.
It is not currently natively possible to configure firmware when using Terraform as the deployment method. This setting may be configured in conjunction with use of the Cloud UI or the Kubernetes CLI. Alternatively, you may extend the Virtual Server Terraform module yourself.