Galactic VPC is in preview, and the
networking.datumapis.com/v1alpha API can change.Limitations
In addition to the networking limitations that apply to all of Compute, networks have the following limitations:- Each workload attaches to exactly one network through one network interface, and it can’t move to another network.
- Instance addresses aren’t reachable from the internet. To serve traffic publicly, attach an ALB to the workload.
- The
networkPolicyfield of a network interface has no effect. Don’t rely on it to restrict traffic. Firewall rules are a planned capability. - You can’t choose a network’s address ranges or create your own subnets.
- Networks carry Compute traffic only in the locations where Compute runs:
us-central-1,us-east-1, andus-west-1.
Planned capabilities
Datum is working on the following networking capabilities:- Outbound internet access: Per-network control of internet access from Instances, starting with IPv6 destinations, and visibility into the address that the traffic leaves from.
- IPv4 destinations: Access to internet services that have only IPv4 addresses, from Instances that have only IPv6 addresses.
- Firewall rules: Security groups that control the traffic to and from your Instances.
- Private DNS: Private DNS names, so Instances can find each other without IP addresses.
- Networks in the portal: Viewing and managing networks in the Datum Cloud portal.
Plans can change. This list isn’t a commitment to deliver any feature or to meet any timeline.
What’s next
- To learn which traffic a network carries, see Network addressing and traffic.
- To serve a workload publicly through Datum’s ALB, see Publish a workload.
- To run Instances in more locations, see Placement and scaling.