Skip to content

docs: add IPv6 readiness guidance for Compute - #118

Open
dlotterman wants to merge 1 commit into
mainfrom
dlott_agents+ipv6
Open

dlotterman wants to merge 1 commit into
mainfrom
dlott_agents+ipv6

Conversation

@dlotterman

@dlotterman dlotterman commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Compute and gVPC are IPv6 only. Agents and users keep running into problems because apps bind to IPv4 (0.0.0.0, listen 80;) or connect to IPv4 addresses, and the docs don't say so until a deploy fails.

This PR puts the guidance where people and agents look first, without adding a new page.

  • Compute troubleshooting: new "IPv6 readiness" section with the pre-deploy checklist, bind examples for nginx, Node.js, Python, and Go, a local ss check, and steps for agents.
  • Compute overview: short "IPv6 readiness" section that links to the troubleshooting section, and a note that Instances are IPv6 only.
  • First-workload tutorial and ALB prerequisites: link to the readiness section.

Review notes

  • The server examples come from general knowledge, not from a live Datum deploy. Please check them, especially the Node.js, Python, and Go snippets.
  • Nothing here changes the Compute API or behavior. It only documents existing IPv6-only networking.

@mintlify

mintlify Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Datum 🟢 Ready View Preview Nov 4, 2026, 7:22 PM

Compute and gVPC are IPv6 only. Apps that bind to IPv4 (0.0.0.0,
listen 80;) or connect to IPv4 addresses fail, and the docs didn't say
so until a deploy failed.

- Add an "IPv6 readiness" section to Compute troubleshooting with the
  pre-deploy checklist, bind examples, a local check, and steps for agents.
- Add a short "IPv6 readiness" section to the Compute overview that links
  to it, and note that Instances are IPv6 only.
- Link the first-workload tutorial and the ALB prerequisites to the
  readiness section.
- Tell agents on the deploy-workloads page to search the app's code and
  config for IPv4 addresses before they deploy, and note in the
  configuration page that env values should use hostnames.
@cla-assistant

cla-assistant Bot commented Nov 4, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

This branch was successfully deployed

1 active deployment
staging — fd3687bd Deployed Nov 4, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant