Compute limitations and roadmap

​

Limitations

​

Runtime and sizing

• One instance type is available, and you can’t set CPU or memory for each container.
• Persistent disks, raw devices, GPUs, and custom virtual machine images aren’t available. Files written at runtime are lost when Datum replaces an Instance.
• Instances with more than one container aren’t supported. Run one container per workload.
• Health probes, such as readiness and liveness checks, aren’t available. An Instance is ready when its containers are running.
• You can’t suspend, resume, or snapshot Instances. You can open a shell or run a command in a running general-purpose Instance; see Instance shell sessions.
• A workload’s runtime class and network can’t change after you create it.

​

Placement and scaling

• Compute runs in us-central-1 (Dallas), us-east-1 (Ashburn), and us-west-1 (San Jose).
• Workloads don’t scale automatically, and they can’t scale to zero. Don’t set scaleSettings.maxReplicas or scaleSettings.metrics.
• Rollouts replace Instances one at a time in each location, with no option to add extra Instances during the rollout.

​

Networking

• During the preview, Instances have private IPv6 addresses only. Private IPv4 addresses and public IP addresses are a preview limitation.
• Private DNS names for Instances are on the roadmap.
• Firewall rules to filter traffic between Instances on a network are on the roadmap.
• Public access is HTTP and HTTPS only, served through Datum’s ALB. Raw TCP and UDP exposure is a preview limitation.

​

Operations

• Read Instance output and ALB access logs in the Cloud Portal or with datumctl compute logs.
• Compute publishes per-Instance CPU and memory measurements. See Observability for the metric names and queries.

​

Roadmap

​

What’s next

• To check quota and fixed limits, see Limits and quotas.
• To fix common problems, see Troubleshooting.