Skip to content
Open
2 changes: 1 addition & 1 deletion alb/limitations-and-roadmap.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The Application Load Balancer is still being built. This page lists known limita
## Limitations

- There is no single composite ALB API yet. An ALB is an `HTTPProxy`, a `TrafficProtectionPolicy`, and optional authentication resources. See [What an ALB is made of](/alb/overview#what-an-alb-is-made-of).
- Public traffic is HTTP and HTTPS only. Raw TCP and UDP exposure isn't available.
- An ALB serves HTTP and HTTPS only. To publish raw TCP or UDP traffic, such as a database or a game server, use a [Network Load Balancer](/nlb/overview).
- Rule exclusions, score thresholds, rate limiting, and circuit breaking aren't available through `datumctl alb`. Use manifests. See [Web application firewall](/alb/configuration/waf).
- A `connector` backend must be the only backend in its rule.
- You can't choose which Datum locations serve a load balancer or set its capacity. [Envoy](/platform/envoy) in every location serves every load balancer, and Datum scales the fleet.
Expand Down
2 changes: 1 addition & 1 deletion alb/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,14 @@

Datum's Application Load Balancer (ALB) is an edge proxy built on [Envoy](/platform/envoy), with a [Coraza](https://www.coraza.io/)-based [web application firewall](/alb/configuration/waf) (WAF). It started life as Datum's "AI Gateway", and it's built for AI and agent traffic as much as for websites and APIs.

Application Load Balancers help you protect and route internet traffic to your backend services. We support HTTP(S) 1.1, HTTP/2, HTTP/3, gRPC, and WebSockets. See [How the load balancer handles requests](/alb/request-handling).
Application Load Balancers help you protect and route internet traffic to your backend services. We support HTTP(S) 1.1, HTTP/2, HTTP/3, gRPC, and WebSockets. See [How the load balancer handles requests](/alb/request-handling). For raw TCP or UDP traffic, such as a database or a game server, use a [Network Load Balancer](/nlb/overview) instead.

<Tip>
Running NGINX, Apache, Caddy, or Traefik in front of your app? To replace that container with an ALB, see [Use ALB as your HTTP proxy](/guides/alb-as-httpd).

Check warning on line 16 in alb/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

alb/overview.mdx#L16

Did you really mean 'Caddy'?

Check warning on line 16 in alb/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

alb/overview.mdx#L16

Did you really mean 'Traefik'?
</Tip>

<Frame caption="The overview for a load balancer: whether it is serving, live request rate, error rate, latency and blocked requests, and the hostnames it answers on">
![The Datum Cloud console showing an Application Load Balancer's overview, with live request rate, error rate, p95 latency, requests blocked by the firewall, and a panel for attaching custom hostnames](/images/alb-overview.png)

Check warning on line 20 in alb/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

alb/overview.mdx#L20

Did you really mean 'Balancer's'?
</Frame>

## How it works
Expand Down Expand Up @@ -82,7 +82,7 @@

Each Application Load Balancer deploys with a default hostname and enforces HTTPS (you can disable this).

- **Protection** - The [**OWASP Coraza Web Application Firewall (WAF)**](https://www.coraza.io/) provides built-in protection with the [OWASP Core Rule Set](https://coreruleset.org/), running inside Envoy before requests reach your origin. A load balancer created with `datumctl alb create` starts in `Enforce` mode at sensitivity 1. A `TrafficProtectionPolicy` that doesn't set a mode runs in `Observe` mode. See [Roll out traffic protection safely](/alb/operations/traffic-protection).

Check warning on line 85 in alb/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

alb/overview.mdx#L85

Did you really mean 'Coraza'?
- **Custom Hostnames** – Verify domains (or use already verified domain resources) to use custom hostnames with an Application Load Balancer.
- **Basic Authentication** - Add a username and password to restrict access to an Application Load Balancer.
- **Load Balancing** - Split traffic across several origins by weight, choose the load balancing algorithm, and turn on passive health checks. See [Load balancing and health checks](/alb/configuration/load-balancing).
Expand Down
6 changes: 3 additions & 3 deletions changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@

- **Allowed email domains:** in the organization's **General** settings, owners pick domains from the verified [Domains](/domain-dns/domains) in the organization's projects, and choose the role people get when they join.
- **Clear status:** a badge shows whether joining is **On**, **Paused**, or **Checking**. When joining is paused, a warning gives the reason.
- **Offers, not automatic membership:** people at an allowed domain see an offer in the notification bell, such as "Your **acme.com** email address lets you join **Acme** organization as Viewer". New users see it during onboarding. Nobody joins without accepting.

Check warning on line 50 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L50

Did you really mean 'onboarding'?
- Public email providers can't be used as allowed domains.
- Owners can turn joining off at any time.

Expand All @@ -71,10 +71,10 @@
<Update label="November 13, 2026" description="gVPC" tags={["Fix"]}>
## Fewer network dropouts for instances

Instances on a gVPC network keep their internet access and DNS lookups through two failures that used to interrupt them.

Check warning on line 74 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L74

Did you really mean 'lookups'?

- **No repeated egress blackouts:** replies from the internet to an instance could be dropped for several seconds at a time, over and over, while every component reported healthy. DNS lookups to public resolvers timed out and other internet traffic stalled. Datum now delivers those replies while it relearns the route back to the instance.

Check warning on line 76 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L76

Did you really mean 'lookups'?
- **Moved instances keep DNS:** when an instance was recreated on a different host, its DNS lookups could be denied for minutes. Datum now removes the old host's record of the instance when the instance stops there.

Check warning on line 77 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L77

Did you really mean 'lookups'?

See [gVPC troubleshooting](/galactic-vpc/troubleshooting).

Expand Down Expand Up @@ -109,9 +109,9 @@
<Update label="November 12, 2026" description="datumctl" tags={["Fix"]}>
## Pick the right private zone with `--vpc`

The `datumctl dns` plugin no longer guesses when several zones share a domain, so a record can't land in another VPC's zone.

Check warning on line 112 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L112

Did you really mean 'VPC's'?

- **Ambiguous zones are refused:** every VPC's default private zone is `datum.internal`. When more than one zone matches the domain you typed, the command stops and lists each zone's object name and the VPCs that use it.

Check warning on line 114 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L114

Did you really mean 'VPC's'?

Check warning on line 114 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L114

Did you really mean 'VPCs'?
- **New `--vpc <name>` flag:** uses the zone that VPC resolves. It works on every `record` command and on `zone describe`, `delete`, `nameservers`, `import`, and `export`, for private zones only.
- **Name a zone directly:** pass a zone's object name in place of the domain, for example `datumctl dns record list managed-3f9c2a`.
- Deleting a private zone asks you to confirm with its object name.
Expand All @@ -129,10 +129,10 @@

- **Answers follow your instances:** when an instance is deleted, its old answers disappear within 1 to 2 seconds. A replacement's new address answers about 4 seconds after the instance is ready. Answers are cached for 30 seconds.
- **First lookup answers right away:** new instances get an answer to their first lookup immediately. Before, DNS gave no answer for 0 to 11 seconds after a deploy or restart, and apps that looked up a name at startup failed with `Temporary failure in name resolution`.
- **No failed lookups during rollouts:** DNS stays up through platform restarts, software updates and edge reboots, because servers drain traffic before they stop. Before, a single rollout caused about 75 seconds of failed lookups. Staging rollouts with steady lookups now lose none.

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'rollouts'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'rollouts'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?
- **Several servers per resolver address:** several healthy DNS servers share one resolver address, with health checks, in all three regions. A lost host or edge affects only the instances on that host. Requests to a server on another host now get replies instead of timing out.
- **Status you can trust:** zone status shows within seconds whether your records are being served.
- **Isolation between VPCs:** each VPC's answers are isolated from every other VPC. Removing a zone from a VPC returns `NXDOMAIN`, and deleting a VPC withdraws its access from every DNS server. Only the platform can change which DNS a VPC uses.

Check warning on line 135 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L135

Did you really mean 'VPCs'?

Check warning on line 135 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L135

Did you really mean 'VPC's'?

Private DNS is in preview. See [Private DNS](/domain-dns/private-dns).

Expand Down Expand Up @@ -170,7 +170,7 @@
<Update label="November 10, 2026" description="Application Load Balancer" tags={["Fix"]}>
## New load balancers serve traffic sooner

- **Fixed:** a new ALB no longer returns `503` for several minutes when its compute workload runs in a different location than the edge serving the request. Datum now rebuilds the load balancer's routing as soon as it learns which network the workload is on.

Check warning on line 173 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L173

Did you really mean 'balancer's'?

See [ALB troubleshooting](/alb/troubleshooting).

Expand Down Expand Up @@ -202,7 +202,7 @@
- **Fixed:** deleting a listener works on the first try.
- **Fixed:** the **Add listener** dialog no longer flashes a warning as it closes.

NLBs are early access. See [Network services](/galactic-vpc/networks/network-services).
NLBs are early access. See [NLB operations](/nlb/operations).

Details: [Give the NLB page a traffic path layout](https://github.com/datum-cloud/network-services-operator/pull/890) (#890)
</Update>
Expand Down Expand Up @@ -333,7 +333,7 @@
- **Managed zone:** every network gets its own `datum.internal` zone. Compute publishes each Instance at `<instance-name>.instances.datum.internal`. See [Private DNS for Compute](/compute/private-dns).
- **Your own private zones:** associate private zones with a network for internal names. The zone class is now optional for private zones.
- **Network isolation:** a network can't be pointed at another network's private DNS, and the same names can be reused across networks without leaking answers.
- **Availability:** lookups go only to healthy DNS servers, so server updates no longer stall lookups until they time out.

Check warning on line 336 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L336

Did you really mean 'lookups'?

Check warning on line 336 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L336

Did you really mean 'lookups'?
- **Regions:** a private zone is served only in the regions its networks use, and is withdrawn from regions it leaves.
- **Fixed:** a CNAME that points into another private zone now returns the target's answer over UDP, not just the CNAME.
- **Fixed:** the managed `datum.internal` zone can't be deleted while its network uses it. Deleting a project still removes it.
Expand All @@ -349,14 +349,14 @@

Publish a network service on a public TCP or UDP port with a network load balancer (NLB).

- **Addresses and hostnames:** each location gets a public IPv6 address and a generated hostname you can point a CNAME at. IPv4 is available for single-port listeners where Datum has enabled it.
- **Addresses and hostnames:** each location gets a public IPv6 address and a generated hostname you can point a CNAME at. IPv4 isn't available yet.
- **Health checks:** NLBs actively check backends and send new connections only to healthy ones.
- **UDP ports:** network services now accept UDP ports, and the create-service dialog has a TCP/UDP selector per port. A UDP listener also needs a TCP port on the backend for its health check.
- **Portal:** create an NLB, copy its hostname and address, and add, edit, or delete listeners in the [Cloud Portal](https://cloud.datum.net).

NLBs are early access. TLS listeners aren't supported yet, but a TCP listener forwards TLS traffic unchanged to your backend. Each route serves one backend. An ALB that points at a UDP port now reports a clear unsupported-protocol error.

See [Network services](/galactic-vpc/networks/network-services).
See [NLB](/nlb/overview).

Details: [Add network load balancers to the portal](https://github.com/datum-cloud/network-services-operator/pull/812) (#812)
</Update>
Expand All @@ -380,7 +380,7 @@
When a custom hostname's DNS is hosted outside Datum, the [Cloud Portal](https://cloud.datum.net) now shows whether it points at your ALB.

- **DNS Ready** appears once Datum sees the CNAME or matching IPs pointing at the ALB.
- **Awaiting DNS** appears until then, with a tooltip that names the record to add. The chip no longer spins indefinitely.

Check warning on line 383 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L383

Did you really mean 'tooltip'?
- **Fixed:** an ALB whose single backend carries the Host override can now be edited in the portal instead of showing **Managed with datumctl**.

See [Custom domains](/alb/operations/custom-domains).
Expand Down
1 change: 1 addition & 0 deletions compute/compute-and-alb.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -150,3 +150,4 @@ In addition to the [limitations that apply to all of Compute](/compute/limitatio
- To run in more locations so that more users reach a nearby Instance, see [Placement and scaling](/compute/placement-and-scaling).
- To learn more about `HTTPProxy` routing and options, see [Application Load Balancer](/alb/overview).
- To learn how Instances connect privately, see [Traffic and connecting](/galactic-vpc/networks/traffic).
- To publish a TCP or UDP port that isn't HTTP, such as a database or a game server, see [NLB operations](/nlb/operations).
2 changes: 1 addition & 1 deletion compute/limitations-and-roadmap.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@

- One instance type is available, and you can't set CPU or memory for each container.
- Persistent disks aren't available. The workload API includes a `disk` volume type, but no runtime class serves it, so Datum rejects a workload that declares one. Files written at runtime are lost when Datum replaces an Instance. For details, see [Disk volumes](/compute/configuration#disk-volumes).
- Raw devices, GPUs, and custom virtual machine images aren't available.

Check warning on line 21 in compute/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/limitations-and-roadmap.mdx#L21

Did you really mean 'GPUs'?
- 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.

Check warning on line 23 in compute/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/limitations-and-roadmap.mdx#L23

Did you really mean 'liveness'?
- 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](/compute/instance-shell).
- A workload's runtime class and network can't change after you create it.

Expand All @@ -28,15 +28,15 @@

- 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.

Check warning on line 31 in compute/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/limitations-and-roadmap.mdx#L31

Did you really mean 'Rollouts'?

### Networking

- During the preview, Instances have private IPv6 addresses only. Private IPv4 addresses and public IP addresses are a preview limitation.
- Instances reach IPv4-only internet services by hostname only, through DNS64 and NAT64. A connection to an IPv4 address fails. See [Reach the internet](/galactic-vpc/networks/traffic#reach-the-internet).
- Every Instance can reach the internet, and you can't turn that off. Outbound traffic leaves from shared addresses that Datum doesn't publish, so you can't allowlist your Instances at a destination.

Check warning on line 37 in compute/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/limitations-and-roadmap.mdx#L37

Did you really mean 'allowlist'?
- Firewall rules to filter traffic between Instances on a network are on the [roadmap](/galactic-vpc/limitations-and-roadmap#planned-capabilities).
- Public access is HTTP and HTTPS only, served through Datum's [ALB](/alb/overview). Raw TCP and UDP exposure is a preview limitation.
- Public HTTP and HTTPS traffic reaches Instances through Datum's [ALB](/alb/overview). Public TCP and UDP traffic reaches them through a [Network Load Balancer](/nlb/overview), which is in early access, serves IPv6 only, and is available only in `us-central-1`, `us-east-1`, and `us-west-1`.

For more information about networking, see [gVPC limitations and roadmap](/galactic-vpc/limitations-and-roadmap). To learn which networking capabilities Datum is working on, see [Planned capabilities](/galactic-vpc/limitations-and-roadmap#planned-capabilities).

Expand Down
1 change: 1 addition & 0 deletions compute/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
---

<Note>
**Working with this product via an AI agent?** [Datum MCP](/agents/datum-mcp) gives agents live access to workloads and Instances through its `compute` toolset, including Compute's own diagnostic tools. For an open-ended question such as "why isn't my workload available?", agents can ask [Patch](/datumctl/ai/assistant) with `datumctl assistant chat`.

Check warning on line 8 in compute/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/overview.mdx#L8

Did you really mean 'toolset'?

Check warning on line 8 in compute/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/overview.mdx#L8

Did you really mean 'Compute's'?
</Note>

Datum Cloud Compute runs your app close to your users. You describe what to run and where, and Datum starts isolated Instances in the locations you choose, connects them to a private network, and can serve them publicly through Datum's Application Load Balancer (ALB).
Expand All @@ -20,7 +20,7 @@

- Run an HTTP service or API in more than one location without operating servers.
- Deploy a container image you already build, with virtual machine isolation.
- Start small, purpose-built services in a fraction of a second as unikernels.

Check warning on line 23 in compute/overview.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

compute/overview.mdx#L23

Did you really mean 'unikernels'?

## How it works

Expand Down Expand Up @@ -51,6 +51,7 @@
| Runtime class | The execution tier for a workload's Instances: `general-purpose` or `unikernel`. You choose it when you create the workload. |
| Network | The private network your Instances attach to. `datumctl compute deploy` uses a network named `default`. |
| ALB | Datum's [Application Load Balancer](/alb/overview), which serves public HTTP and HTTPS traffic to your workload's Instances. |
| NLB | Datum's [Network Load Balancer](/nlb/overview), which forwards public TCP and UDP traffic to your workload's Instances. |

## Runtime classes

Expand Down
15 changes: 15 additions & 0 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -194,6 +194,21 @@
],
"expanded": false
},
{
"group": "NLB",
"pages": [
"nlb/overview",
"nlb/configuration",
"nlb/health-checks",
"nlb/traffic-handling",
"nlb/operations",
"nlb/observability",
"nlb/troubleshooting",
"nlb/limits-and-quotas",
"nlb/limitations-and-roadmap"
],
"expanded": false
},
{
"group": "Connectors",
"pages": [
Expand Down
2 changes: 1 addition & 1 deletion domain-dns/operations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ Two rules catch most mistakes:
- **Names are relative.** Use `www`, not `www.example.com`. Use `@` for the domain itself.
- **Targets are absolute.** End every hostname inside a value with a dot: `mail.example.com.`, not `mail`.

For the record types Datum supports, see [Authoritative DNS](/domain-dns/dns). To point a name at a load balancer, see [Point a domain at a load balancer](/domain-dns/point-to-alb).
For the record types Datum supports, see [Authoritative DNS](/domain-dns/dns). To point a name at an Application Load Balancer, see [Point a domain at a load balancer](/domain-dns/point-to-alb). For a Network Load Balancer, see [Use your own domain](/nlb/configuration#use-your-own-domain).

### Set a TTL

Expand Down
3 changes: 2 additions & 1 deletion galactic-vpc/limitations-and-roadmap.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@
In addition to the [networking limitations that apply to all of Compute](/compute/limitations-and-roadmap#networking), 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](/alb/overview) to the workload.
- Instance addresses aren't reachable from the internet. To serve traffic publicly, attach an [ALB](/alb/overview) to the workload for HTTP and HTTPS, or an [NLB](/nlb/overview) for TCP and UDP.
- The `networkPolicy` field 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.

Check warning on line 18 in galactic-vpc/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/limitations-and-roadmap.mdx#L18

Did you really mean 'subnets'?
- Networks carry Compute traffic only in the locations where Compute runs: `us-central-1`, `us-east-1`, and `us-west-1`.
- Every network can reach the internet, and you can't turn that off.
- Outbound internet traffic leaves from addresses that are shared with other Datum customers. Datum doesn't publish them, so a destination can't allowlist your Instances by address.

Check warning on line 21 in galactic-vpc/limitations-and-roadmap.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/limitations-and-roadmap.mdx#L21

Did you really mean 'allowlist'?
- Instances reach IPv4-only internet services by hostname only. A connection to an IPv4 address fails. See [Reach the internet](/galactic-vpc/networks/traffic#reach-the-internet).

## Planned capabilities
Expand All @@ -40,4 +40,5 @@

- To learn which traffic a network carries, see [Traffic and connecting](/galactic-vpc/networks/traffic).
- To serve a workload publicly through Datum's ALB, see [Publish a workload](/compute/compute-and-alb).
- To publish a TCP or UDP port, see [NLB operations](/nlb/operations).
- To run Instances in more locations, see [Placement and scaling](/compute/placement-and-scaling).
40 changes: 38 additions & 2 deletions galactic-vpc/networks/network-services.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
description: "Give a workload's Instances a stable name and named ports on a gVPC network, and send load balancer traffic to them."
---

A network service gives a workload's Instances on one network a stable name and named ports. Datum keeps the service's membership current as Instances start, stop, and move between locations, and sends each request to the nearest location that has a ready Instance. Datum's [Application Load Balancer](/alb/overview) reaches a workload through a network service.
A network service gives a workload's Instances on one network a stable name and named ports. Datum keeps the service's membership current as Instances start, stop, and move between locations, and sends each request to the nearest location that has a ready Instance. Datum's [Application Load Balancer](/alb/overview) and [Network Load Balancer](/nlb/overview) reach a workload through a network service.

<Note>
gVPC is in preview, and the `networking.datumapis.com/v1alpha` API can change.
Expand All @@ -15,7 +15,7 @@
A network service is a `NetworkService` resource with two parts:

- **A selector:** labels that an Instance's network interface must carry to belong to the service. Every Instance of a workload carries the workload's name as a label, so a service usually selects one workload.
- **Ports:** the ports the Instances listen on, each with a name, such as `http` on port `8080`. A load balancer refers to a port by its name, not its number.
- **Ports:** the ports the Instances listen on, each with a name, a number, and a protocol, `TCP` or `UDP`, such as `http` on TCP port `8080`. A load balancer refers to a port by its name, not its number.

Keep the following points in mind:

Expand Down Expand Up @@ -51,13 +51,15 @@

To add more ports, repeat `--port`. A service takes up to 16 ports, and each name and number must be unique.

`datumctl network service create` creates TCP ports only. To add a UDP port, use the Cloud Portal or a manifest. See [Add UDP ports](#add-udp-ports).

By default, a load balancer connects to a port over HTTP/1.1. For a port that serves gRPC or another HTTP/2 app without TLS (h2c), use the long form of `--port` with `app-protocol=h2c`, such as `--port=name=grpc,port=9090,app-protocol=h2c`. The load balancer then sends every request on that port as HTTP/2. Most servers accept WebSockets only over HTTP/1.1, so serve WebSockets on a different port.

To select Instances by label instead of by workload, use `--selector`, such as `--selector app=web`. The labels must be on the Instances' network interfaces, not only on the workload.

## Send load balancer traffic to a network service

To send a load balancer's traffic to a network service, name the service and one of its port names:

Check warning on line 62 in galactic-vpc/networks/network-services.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/networks/network-services.mdx#L62

Did you really mean 'balancer's'?

```bash
datumctl alb create LOAD_BALANCER_NAME \
Expand All @@ -67,6 +69,37 @@

For more information, see [Create a load balancer](/alb/operations/overview#create-a-load-balancer).

To publish a port on a public TCP or UDP port, send a [Network Load Balancer](/nlb/overview)'s traffic to it with a route instead. A route names the service and one of its port names, and the port's protocol must match the NLB listener's. See [Routes](/nlb/configuration#routes).

## Add UDP ports

To give a service a UDP port, such as for an NLB, describe the service in a manifest and set `protocol` on each port. The following service has a UDP port for a game server, and a TCP port for the NLB's health check:

Check warning on line 76 in galactic-vpc/networks/network-services.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/networks/network-services.mdx#L76

Did you really mean 'NLB's'?

```yaml game-service.yaml
apiVersion: networking.datumapis.com/v1alpha
kind: NetworkService
metadata:
name: game
spec:
networkInterfaces:
selector:
matchLabels:
compute.datumapis.com/workload-name: game
ports:
- name: game
port: 7777
protocol: UDP
- name: health
port: 8080
protocol: TCP
```

The `compute.datumapis.com/workload-name` label selects every Instance of the named workload. To create the service, run `datumctl apply -f game-service.yaml`.

In the [Cloud Portal](https://cloud.datum.net), the create-service dialog has a **TCP** or **UDP** choice for each port.

An ALB can't send traffic to a UDP port.

## Check a network service

To see what a service selects, its ports, and where it's serving, run the following command:
Expand Down Expand Up @@ -109,8 +142,11 @@

Before it asks you to confirm, the command lists the load balancers that send traffic to the service. Those load balancers stop reaching anything on that route.

Deleting a network service with `datumctl delete networkservice` doesn't check for NLB routes. An NLB whose route uses the service stops serving, and the route reports `BackendNotFound`. See [Delete an NLB](/nlb/operations#delete-an-nlb).

## What's next

- To manage networks and Instances' network interfaces from the command line, see [Operations](/galactic-vpc/operations).
- To publish a workload with a load balancer in one step, see [Compute and ALB](/compute/compute-and-alb).
- To publish a TCP or UDP port, see [NLB operations](/nlb/operations).
- To learn how Instances connect privately, see [Traffic and connecting](/galactic-vpc/networks/traffic).
2 changes: 1 addition & 1 deletion galactic-vpc/networks/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ A network belongs to a project, not to a location. The following list describes
- **Many workloads on one network:** Several workloads can name the same network. For example, a frontend workload and a backend workload can share a network.
- **Addresses are private IPv6:** Each network gets its own private IPv6 prefix from the unique local address range. Each Instance gets an address from that prefix. The addresses aren't reachable from the internet. For more information, see [Addressing](/galactic-vpc/networks/addressing).
- **Networks are isolated:** Each network is separate from every other network, including other networks in the same project and other customers' networks.
- **Public traffic arrives through Datum's ALB:** To serve a workload on the internet, attach Datum's [Application Load Balancer](/alb/overview) to it. The ALB reaches a workload through a [network service](/galactic-vpc/networks/network-services), which gives the workload's Instances a stable name and named ports, and forwards each request to an Instance over the private network. For more information, see [Compute and ALB](/compute/compute-and-alb).
- **Public traffic arrives through a load balancer:** To serve a workload on the internet, attach Datum's [Application Load Balancer](/alb/overview) to it for HTTP and HTTPS, or a [Network Load Balancer](/nlb/overview) for raw TCP and UDP. The ALB reaches a workload through a [network service](/galactic-vpc/networks/network-services), which gives the workload's Instances a stable name and named ports, and forwards each request to an Instance over the private network. For more information, see [Compute and ALB](/compute/compute-and-alb).

## The default network

Expand Down
2 changes: 1 addition & 1 deletion galactic-vpc/networks/traffic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@
| Between Instances on the same network in different locations | Yes | A network spans locations, and Instances can connect to each other privately across locations using their private IPv6 addresses. |
| Between different networks | No | Networks are isolated from each other. |
| To or from other addresses through an Instance | No | A network only delivers a packet addressed to an Instance's own address, and only accepts a packet from an Instance's own address. An Instance can't route traffic for other addresses, so a router or VPN appliance needs an overlay, such as VXLAN or a UDP tunnel, between Instances. |
| Inbound from the internet | Through Datum's ALB | Instance addresses aren't reachable from the internet directly. Public HTTP and HTTPS traffic reaches Instances through Datum's [Application Load Balancer](/alb/overview). Raw TCP and UDP exposure is a preview limitation. |
| Inbound from the internet | Through a load balancer | Instance addresses aren't reachable from the internet directly. Public HTTP and HTTPS traffic reaches Instances through Datum's [Application Load Balancer](/alb/overview). Public TCP and UDP traffic reaches them through a [Network Load Balancer](/nlb/overview), over IPv6. |
| Outbound to the internet | Yes | Instances can reach internet destinations over IPv6, and services that have only IPv4 addresses by hostname. See [Reach the internet](#reach-the-internet). |
| Lookups by name | Yes | Instances resolve public names, and the [Private DNS](/domain-dns/private-dns) names of other Instances on the same network, such as `web-default-us-central-1-0.instances.datum.internal`. |

Check warning on line 24 in galactic-vpc/networks/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/networks/traffic.mdx#L24

Did you really mean 'Lookups'?
| Firewall filtering | Not in the preview | Firewall rules to filter traffic between Instances on a network are on the [roadmap](/galactic-vpc/limitations-and-roadmap#planned-capabilities). |

The workload API accepts a `networkPolicy` field on each network interface, but the field has no effect. Don't rely on it to restrict traffic. To limit who can reach a service, check credentials in your app, or put services that must stay apart on different networks. Firewall rules for networks are on the [roadmap](/galactic-vpc/limitations-and-roadmap#planned-capabilities).
Expand Down Expand Up @@ -49,7 +49,7 @@

- **Connect to IPv4 services by hostname, not by IPv4 address.** An Instance has no IPv4 address or route, so a connection to an IPv4 address such as `203.0.113.10` fails. If a service has only a public IPv4 address and no name, create an `A` record for it in a public [DNS zone](/domain-dns/dns) you control, and connect by that name. Private IPv4 addresses, such as `10.0.0.5`, aren't reachable.
- **Use the DNS resolvers that the Instance is given.** Datum configures resolvers that perform DNS64. In a `general-purpose` Instance, they're in `/etc/resolv.conf`. An app or image that uses its own resolver without DNS64, such as DNS over HTTPS or a hard-coded public resolver, gets only IPv4 addresses for IPv4-only names, and can't connect to them. The resolver addresses can change, so don't hard-code them.
- **Outbound traffic leaves from shared addresses.** The Instances in a location share their outbound addresses with each other and with other Datum customers. Datum doesn't publish these addresses, and they can change. Don't ask a destination to allowlist them. Authenticate to the destination instead, for example with an API key or a client certificate.

Check warning on line 52 in galactic-vpc/networks/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

galactic-vpc/networks/traffic.mdx#L52

Did you really mean 'allowlist'?
- **You can't turn off internet access.** Every Instance can reach the internet. A setting to turn off internet access for a network is on the [roadmap](/galactic-vpc/limitations-and-roadmap#planned-capabilities).

## What's next
Expand Down
2 changes: 1 addition & 1 deletion galactic-vpc/operations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ If Instances still hold addresses on the network, the network stays in deletion

## Manage network services

The `datumctl network service` commands create, describe, change, and delete network services. For more information, see [Network services](/galactic-vpc/networks/network-services).
The `datumctl network service` commands create, describe, change, and delete network services. They create TCP ports only. For UDP ports, which a [Network Load Balancer](/nlb/overview) can publish, use a manifest. For more information, see [Network services](/galactic-vpc/networks/network-services).

```bash
datumctl network service create api --workload=api --port=http:8080
Expand Down
Loading
Loading