Configuration Options
Configure and deploy Virtual Servers using one of four deployment methods
Deployment methods
Virtual Servers may be configured and deployed using four distinctive methods. Learn more about how to set up each of the deployment methods covered in this implementation guide by visiting their respective pages under the Virtual Server Deployment Methods section.
Our in-house, graphical Web-based interface for configuring Virtual Servers. Configuration options are represented either as graphical selection options, or as fields that can be configured in the YAML manifest from the UI.
⛵ Kubernetes CLIDeploy Virtual Servers using the standard way of interacting with Kubernetes, via kubectl
. Configuration options are implemented as fields in the YAML manifest file.
HashiCorp's infrastructure-as-code tool can deploy Virtual Servers by leveraging CoreWeave's Virtual Server Terraform module. Configuration options are implemented using Terraform module configurations.
🖥 Programmatic deploymentInteract with the Kubernetes API directly, using any Kubernetes-compliant SDK. Configuration options are language-specific interactions with the Kubernetes API.
The following configuration options may be changed while the Virtual Server is running:
- Annotations and labels
- Floating IPs
- Root disk size (storage size can only be increased while the Virtual Server is running - it may also take a while before the change is reflected)
How to use this section
Each page beneath this one contains a tabbed table. Each tab explains how to deploy the configurations to your Virtual Server, respective to the method described.
For example:
Examples
Example deployments can be found on CoreWeave's GitHub: