Example usage
Schema
Required
name(String) The name of the VPC. Must not be longer than 30 characters.zone(String) The Availability Zone in which the VPC is located.
Optional
dhcp(Attributes) Settings affecting DHCP behavior within the VPC. (see below for nested schema)egress(Attributes) Settings affecting traffic leaving the VPC. (see below for nested schema)host_prefix(String, Deprecated) An IPv4 CIDR range used to allocate host addresses when booting compute into a VPC. For SUNK clusters, a/18mask is recommended so that host addresses reflect each node’s physical location. SUNK uses this location information to place network-adjacent nodes together, which improves distributed-training performance. Prefixes with a longer mask than/18(for example,/19,/20,/21,/22) don’t carry this location information, so they produce less optimal placement. If you need a different size, CoreWeave can approve one for your account on request. For non-SUNK VPCs, any prefix size is accepted. If left unspecified, a Zone-specific default value will be applied by the server. See Host prefixes for details. This field is immutable once set.host_prefixes(Attributes Set) The IPv4 or IPv6 CIDR ranges used to allocate host addresses when booting compute into a VPC. For SUNK clusters, an IPv4 prefix with a/18mask is recommended so that host addresses reflect each node’s physical location. SUNK uses this location information to place network-adjacent nodes together, which improves distributed-training performance. Prefixes with a longer mask than/18(for example,/19,/20,/21,/22) don’t carry this location information, so they produce less optimal placement. If you need a different size, CoreWeave can approve one for your account on request. For non-SUNK VPCs, any prefix size is accepted. See Host prefixes for details. (see below for nested schema)ingress(Attributes) Settings affecting traffic entering the VPC. (see below for nested schema)vpc_prefixes(Attributes Set) A list of additional prefixes associated with the VPC. For example, CKS clusters use these prefixes for Pod and service CIDR ranges. (see below for nested schema)
Read-Only
id(String) The unique identifier for the VPC.
Nested Schema for dhcp
Optional:
dns(Attributes) Settings affecting DNS for DHCP within the VPC (see below for nested schema)
Nested Schema for dhcp.dns
Optional:
servers(Set of String) The DNS servers to be used by DHCP clients within the VPC.
Nested Schema for egress
Optional:
disable_public_access(Boolean) Specifies whether the VPC should be blocked from consuming public Internet.
Nested Schema for host_prefixes
Required:
name(String) The user-specified name of the host prefix.prefixes(List of String) The VPC-wide aggregates from which host-specific prefixes are allocated. May be IPv4 or IPv6.type(String) Controls network connectivity from the prefix to the host. Must be one of:PRIMARY,ROUTED,ATTACHED.
ipam(Attributes) The configuration for a secondary host prefix. (see below for nested schema)
Nested Schema for host_prefixes.ipam
Required:
prefix_length(Number) The desired length for each Node’s allocation from the VPC-wide aggregate prefix.
gateway_address_policy(String) Describes which IP address from the prefix is allocated to the network gateway. Must be one of:UNSPECIFIED,EUI64,FIRST_IP,LAST_IP.
Nested Schema for ingress
Optional:
disable_public_services(Boolean) Specifies whether the VPC should prevent public prefixes advertised from Nodes from being imported into public-facing networks, making them inaccessible from the Internet.
Nested Schema for vpc_prefixes
Required:
name(String)value(String)