VPC Networks Overview
Crusoe Cloud is currently in private beta. If you do not currently have access, please request access to continue.
Crusoe Cloud provides a high performance Software Defined Network (SDN) for developers.
Concepts
Default networks and subnets
Currently, you are limited to a single, default VPC network and the default, regional VPC subnets that are automatically created for you when you create a project. At present, these look like:
Network | CIDR |
---|---|
default-vpc-network | 172.27.0.0/16 |
Subnets | CIDR |
---|---|
default-subnet-us-northcentral1-a | 172.27.0.0/20 |
default-subnet-us-east1-a | 172.27.16.0/20 |
Reserved IPs within subnets
We currently reserve the first five IPs within a subnet (e.g. 172.27.0.0
through 172.27.0.4
) as well as the broadcast address (e.g. 172.27.0.255
).
IP lifecycle
Public IPs are tied to the lifecycle of the VM, and change if a VM is stopped and started. Private IPs are static, and will not change based on the lifecycle of the VM.
Internal DNS
By default, we provide internal DNS for all VMs within a VPC network. VMs are reachable at $VM_NAME.$LOCATION.compute.internal
, e.g. stable-diffusion-serving.us-northcentral1-a.compute.internal
.
Limitations
IPv4 only
Currently, we only support IPv4.
Static IPs
Currently, all private IPs are static, while all public IPs are dynamic by default, and change during a VM stop and restart. Static IPs are available via private alpha, and if you are interested in getting these enabled for your account, please contact Support.
Non-default networks
Currently, we only support the default networks. We expect this to change in the near future.
Communication limited to within the subnet
Currently, subnet-to-subnet communication using private IP addresses is limited to a single region. If you want your workloads in in different regions to talk to each other, you can use Public IP addresses, assigned to those workloads. We suggest configuring proper firewall entries to ensure you're allowing traffic only from the expected workloads.